Hello, is anyone using swat to manage samba? I am trying to get swat going but it needs an entry in /etc/inetd.conf for which there is no file. It looks like Gentoo puts everything in init.d but how do you start swat??

The package fails to install inetd.conf where it should be . inetd is installed by default as part of the netkit-base package (so don't go installing xinitd unless you prefer it ). The normal sample inetd.conf can be found in " /usr/doc/netkit-base-0.17-r6/samples/inetd.conf.gz"

After looking at this thread, I have noticed that no one has answered the original question...which was basically, "How do I start SWAT with inetd.conf (because it is missing)."

The inet daemon is installed with netkit-base. Therefore, I believe every Gentoo user should have this. The quirky thing about all of this is that Gentoo does not seem to ship with a 'standard' inetd.conf file. The reasons for this are probably because of the safety precautions and the rc-update scripts.

Sadly yet, it does not seem that the Gentoo maintainer has not created a rc-update compatible script yet. It would be easy to make, but time is always a consideration, because there is never enough of it .

So, we are left to either using xinetd or standard inetd. In order to use the xinetd, you need to emerge it first. Then it should work almost magically, because it seems that the Gentoo samba maintainer created a swat xinetd.d configuration.

But for us ppl that think old is good, we get the shaft . Ahh well, here are the steps to make life a little easier and less confusing.

1.) 'emerge samba'
2.) Do the following 'rc-update add inetd default'. This will add the inet daemon to start during bootup.
3.) Create a new inetd.conf file, and copy the contents of 'man swat' for the inetd configuration. Make sure to have the correct path information.
4.) Do a 'smbpasswd -a root' or you will not be able to login to your shiny new samba install.

Go ahead and reboot. SWAT should now automatically start and you can connect to it via http://localhost:901

I hope this helps, and I'm pretty sure in the future there we be a change and an addition of a rc-update script for starting swat.

I really need to learn what you have to do in various situations to avoid rebooting. When to 'source' what,
the [x]inetd restart as you mentioned and whatever else there might be._________________lolgov. 'cause where we're going, you don't have civil liberties.

I really need to learn what you have to do in various situations to avoid rebooting. When to 'source' what,
the [x]inetd restart as you mentioned and whatever else there might be.

Well, if you're reconfiguring a service, restarting it generally does the trick. If something changes the environment variables (installing X, for instance, which adds path entries and stuff), source /etc/profile will usually get your shell up-to-date. Linux is a very stable operating system, and in most cases you don't have to reboot unless you're switching kernels or your hardware craps out.