When users try and configure swat to run, a "connection refused" at localhost:901 error is persistent! In order to run swat, the xinetd module must also be installed. This should be a RDEPEND in the ebuild IMHO Reproducible: Always Steps to Reproduce: 1. emerge samba 2. change DISABLED = YES to NO in /etc/xinet.d/swat 3. try http://localhost:901 Actual Results: Browser reports "Connection Refused at localhost:901" or similar Expected Results: Swat configuration utility is available After emerging xinetd, the user must do rc-update add xinetd default emerging xinetd resolves the problem! So, even though swat is installed but disabled by default, xinetd should be installed with it!
Swat isn't a necessary part of samba; the smb.conf can be edited with any text editor or via the IDEALX Management Console. Maybe a "swat" use flag should be considered but I disagree with adding xinetd as a dependency for a default installation.
Perhaps so, but swat IS delivered with Samba. And, if the user tries to get it working, it cannot work without the xinet dependency being resolved. To a newbie or uninitiated, this can cause some frustration. If you don't want to add the dependency, at least add an einfo message at the end of samba's install saying that to use swat, be sure xinetd is installed. JM2C
how about a local use flag for samba ? if use "swat" -> then inlude xinetd in the RDEPEND ? Unfortunately there is no configure option in samba to disable swat completely ...
not sure yet how to handle this bug. I don't like forcing the xinetd dependency though.
While indeed SWAT is often referenced in the samba docs to use for configuring samba, it is an optional component and not required for full samba configuration and functionality. I'm not against an optional SWAT USE flag which may force an xinetd install, or a Portage magic "no xinetd just for SWAT" workaround, but I don't use xinetd on my systems and would love to not have to surgically remove the xinetd RDEPEND for every future bump. Thank you.
I vote for either 1) RTFM: leaving the ebuilds as they are 2) swat use flag: this is a bit tricky, since swat is mixed with docs. If one uses '+swat -docs', care should be put in pkg_install to not remove swat functionality while removing docs (so this is, maybe, the rise of new bugs(tm) :-) ).
Yes, please do not make samba depend on (x)inetd. That's bloat. Christian's suggestion is good, I think. Or maybe force "doc" on the user if he uses "swat" ;-) Actually I'd think it would be sufficient to ewarn the user that in case he wants tu use swat he should now emerge (x)inetd ...
samba-3.0.20b has 'swat' USE flag, which forces xinetd dependecy. Please reopen if needed
