>Seems this forum do not have many people look around, anyway just wish someone can see this message and maybe can help me out.
>
>I have just installed SAMBA 2.2.1a on RedHat, I just follow the install guild step by step to do it, but when I need to edit the inetd.conf to activate the SWAT function, I can't find the file! I do not have inetd.conf in my system.. what can I do now? Please help!
>
>Jimi

It is usually in /etc/inetd.conf, along with the other configuration files. If it is not there then someone (:)), with root priviledges, rm'd it.

See: http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap5sec36.html You may be able to restore it from your install CD, or you can go to the RH website and download a copy from their ISO directory.

Also, there is a utility called 'locate' which allows you to find any file, even by a fragment of its name. That utility uses a database called locatedb and is updated automatically by a cron entry once a day. Cron is like an auto batchfile update system. If you don't keep your computer on long enough and cron doesn't fire, then you can su to root and run 'updatedb' to update the locate database. So, as user, you could have typed 'locate inetd.conf' and a complete pathway listing to the file would be displayed. Also, there is another utility called 'whereis', a utility which knows where executable files are, and gives the complete pathway when ased. Some distros give 'whereis' the ability to report the exact locations of any file. Asking 'whereis inetd.conf'
may give you the complete path to inetd.conf. The big difference between locate and whereis: Say you used 'locate rpm' because you wanted to find where that utility was located. You will get a ton of files listed because 'rpm' may be in part of many apps name, or an extension to many rpm files. Using 'whereis rpm' will give just the locations where the rpm executable is located.
JLK