Also, if you choose to put netprobe in the init.d startup directory you will need to change lines 151 and 164 of the startup script to reflect the location of the users.txt file to /opt/netprobe/config...
I have mine resetting every two hours which explains the crashes. The file could not be found. The way the script is presently written, it expects to be started from the /opt/netprobe directory. Regards, John C. On Tue, 2003-03-18 at 04:40, Jon Blakely - CTS Howick wrote: > Cyrus, > > I would be consider creating a server-manager panel that will allow a user > to stop/start/retart netprobe and choose the ethernet port to probe. > The reason I say this is that if you have netprobe start via init.d or > rc.local on reboot you immediately have an ethernet port running in > promiscuous mode. You could say we will make sure only eth0 starts as it by > default the local network but some users have configured the other way. I > believe that running an eth port, particularly one facing the world wide > web, in promiscuous mode can be a security risk. > While you have the option in the netprobe interface to stop a port, it only > stops the logging. > > Jon Blakely > > > -----Original Message----- > > From: Cyrus Bharda [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 18, 2003 11:51 AM > > To: E-Smith Developers List > > Subject: Re: [e-smith-devinfo] [BETA] Need constructive critisism on a > > howto > > > > > > 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? > > > > 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 > > > > > > > > > -- > 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 -- John Cusick <[EMAIL PROTECTED]> -- 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
