On Mon, 2003-03-17 at 18:50, Cyrus Bharda wrote: > Ok which is the right way this way from Graham: > > : I think you just need to add the start command > : /opt/netprobe start eth1 > : to /etc/rc.d/rc.local > : this is where squidguard is loaded when my server starts > > Or this way from John: > > : Copy netprobe to /etc/init.d and then create a symlink to netprobe in > : /etc/rc7.d/ > : > : # ln -s /etc/init.d/netprobe /etc/rc7.d/S95netprobe > > Because I can understand Graham's way but dont understand how you tell > netprobe to start on the network device using John's way?
Cyrus, Technically, all programs listed in rc7.d start when the esmith system first boots (unless you have specifically turned a service off such as appletalk in my case). They are symlinks to all the daemon startup scripts on your system which are located in the /etc/init.d directory. For example also, when you start a standard redhat system in console/multi-user mode, all programs in /etc/rc3.d are started or in X/multi-user mode, all programs in /etc/rc5.d are started. These too are symlinks to the programs/daemons located in /etc/init.d. So for example, even though you may have 30 or 40 startup scripts listed in the init.d directory, only the ones symlinked in your default initiation mode (and in e-smith/sme's case, that is init 7) will start. This is a rough explanation, but generally true. Take a look at your /etc/rc7.d directory and you will see links to all the scripts that start on your e-smith system when you first boot up. Then take a look at all the scripts in the /etc/init.d directory and you will see there are a few more than exist in the rc7.d There are some good documents concerning the bootup process at http://www.tldp.org/ that explain how the system boots and runs in detail, in particular the SAG and NAG docs (System Admin Guide and Network Admin Guide) Regards, John C. > netprobe hasn't crashed on me since I last started it 27 hours ago, but then > again I dont really know how to see if it has crashed or not, its always > worked when I try to access the stats via the webpage, doesn't that mean > that it hasn't crahsed? Anyone else getting this crahing problem? > > : I notice a problem here... netprobe has crashed once today after about > : 6 hours of run time. I will continue to watch it > > Thanks again for everyone's input :-) > > Cyrus Bharda > -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
