Nope... it works just like most other configuration files, except that what we really do is stuff the lines (ignoring comments, that is anything from the # to the end of the line) back into a long string and then reparse it to get back an argc argv[] just as it you had typed the whole fool thing on the command line.
So .../ntop -i a,b,c @/etc/ntop.conf -u ntop where /etc/ntop.conf is # garbage # -i a,b -i a,b,c,d --trace-level 3 becomes as if you typed: .../ntop -i a,b,c -i a,b,c,d --trace-level 3 -u ntop (note that for valued options, only the last one matters, so this is equivalent to .../ntop -i a,b,c,d --trace-level 3 -u ntop) But that's not your problem - the error sounds like ntop is unable to OPEN the file, not having problems processing it. In the future, cut and paste the entire message line, not portions of it and don't paraphrase. If it's what I think it is, it's just being reflected back from the OS on an fread(). Search the back traffic - we have had somebody else with problems getting the file read... -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Donovan Steen Sent: Thursday, July 10, 2003 9:37 AM To: [EMAIL PROTECTED] Subject: [Ntop] ntop.conf? When editing the ntop.conf file, I of course remove the # on each config option, there is also a "- -" before each parameter, should these be removed also? I am getting a fatal error: unable to open configuration file @/etc/ntop.conf Thanks Donovan _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
