Glad it's fixed... Don't forget to remove the \s too - they're unnecessary also...
As the accident investigators call it, a case of CFIT (Controlled Flight Into Terrain). Don't sweat it. Sadly, I've done it myself more than a few times... That's why _DEBUG lines work (something about incontrovertible evidence, even when you're sure things are ok)... -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roy S. Rapoport Sent: Monday, June 23, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: [Ntop-dev] ntop 2.2 on Solaris 9 - @filename On Mon, Jun 23, 2003 at 10:47:50AM -0500, Burton M. Strauss III wrote: > The PARAM_DEBUG stuff shows EXACTLY what is read from the file, ntop_args in > the current directory (bad choice, BTW, use absolute paths or else when ntop > starts in a script, etc. it won't find the file)... Yup -- right now, this is just debugging. > You know, it reads as if your ntop_args was a shell script, and looked like > this: > > ------------------------------------ > @!/bin/sh > /usr/local/ntop/bin/ntop \ > -P /usr/local/ntop \ > -u ntop \ > etc. > ------------------------------------ Nope. Actually -- whoops, first line's "/usr/local/ntop/bin/ntop" I *knew* it should just have args -- I just screwed this one up. Works now. _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
