There are differences 'tween the ntop package .gz and the (semi-official) rpms I create and post at SourceForge.
The ntop script in init.d started as just a minimal script with hard coded settings designed to be configured by the user. The version that's there now is a little smarter. The version I personally use is customized to my needs across platforms and is a little smarter still. I've attached two of my versions, plus the one you originally sent (which people haven't yet seen). ntop.tigger.2 is the basic script lightly modified (the 'extra' parms IIRC). ntop.tigger is the one I use. It adds the ability to grab a list of interfaces and check the sysconfig/network-scripts files for an ntop= line, to build the interface list. What you're proposing is to make it a 'real' script, one that knows how to read ntop.conf and other configuration files. Combine what you're doing with my stuff and it would be a lot more useful. Sounds like a good idea, go to it! -----Burton > -----Original Message----- > From: pc [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 26, 2003 9:07 PM > To: [EMAIL PROTECTED] > Subject: Issues w/ ntop 2.2.93 <snip/> > --access-log ownership error> > > The ntop user needs to own the file specified in the access log option. /etc/rc.d/init.d/ntop has been improved to take care of this (below). <snip/>
ntop.tigger.2
Description: Binary data
ntop.tgm
Description: Binary data
ntop.tigger
Description: Binary data
