It works for me on RH7.3, 8 and 9 -- plus six other Linuxes and FreeBSD. It
has to be something in your configuration. I think, based on your various
comments, that you don't understand - -L and --use-syslog=xxxxxx are the
same (in that they're the short and long version of the 'same' option, yet
they're independent because of the need to process the parameter.
If you give more than one, only the right most in the option string will
matter.
So "--use-syslog=local3 -L" is really just -L
>From main.c:
case 'L':
myGlobals.useSyslog = DEFAULT_SYSLOG_FACILITY;
break;
and
case 131:
if (optarg) {
int i;
stringSanityCheck(optarg);
for (i=0; myFacilityNames[i].c_name != NULL; i++) {
if (strcmp(optarg, myFacilityNames[i].c_name) == 0) {
break;
}
}
if (myFacilityNames[i].c_name == NULL) {
printf("WARNING: --use-syslog=unknown log facility('%s'), using
default value\n",
optarg);
myGlobals.useSyslog = DEFAULT_SYSLOG_FACILITY;
} else {
myGlobals.useSyslog = myFacilityNames[i].c_val;
}
} else {
printf("NOTE: --use-syslog, no facility specified, using default
value. Did you forget the =?\n");
myGlobals.useSyslog = DEFAULT_SYSLOG_FACILITY;
}
break;
If the facility name you gave is missing, you should see - printed to the
console - an error message. Otherwise, it should set to the value you gave.
If you forget the =s, --use-syslog is equivalent to -L.
> -----Original Message-----
> From: pc [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 10:16 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Issues w/ ntop 2.2.93
>
> I'm resending this message directly where the ntop-devel mailing list
quarantined it for the moderator due to its size. Nothing happened with the
previous for more then 24hrs. I also did a little more editing and added
another attachment, so you can have the moderator delete the first message.
>
> -----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
>
> The other day I loaded 2.2.93 on my machine and there are a variety of
issues that I have found. I'm a newbie around here, so please be a little
patient. With the call for comments ASAP, I thought I would pass this along
quickly instead of getting better acquainted with the group first. I'm not
a networking expert and I'm not a c coder either, but I thought that my
experience as a unix/NT SA could be of some use.
>
> First, my environment: The RedHat source> rpm was downloaded and rebuilt
on an RedHat 9 system. The system has all the latest RedHat updates
installed including the latest kernel. The only thing that I changed in the
ntop.spec was the release number so I don't screw up down the street
(changed to local1 - a convention I use for locally compiled rpms). This
means that NPTL is active. I've attached a copy of the output du> ring the
rebuild (see ntop.build.redhat9.rpm.txt). There were no problems
encountered with the rebuild process and the install via rpm was also fine.
There were a few issues with new vs. old file locations where the previous
release was 2.2c from a cvs download.
>
> This box is somewhat of a toy I use for keeping up with what's happening
in the linux world but I also use it for some valid development at times. I
have a few services running (secondary DNS, NTP, backup DHCP, etc) for my
relatively tiny home network (10 nodes). But I do have a couple of routers
on the network and a Cabletron ELS100 switch, so I can do some advanced
playing around. Linux firewall features are currently not running on this
machine. rrdtool is installed but I'm not currently using it. A PR form is
attached for further info (see: myconfig_20030826.txt)
>
> So here are some things that I've come up with:
>
> --use-syslog option not working
>
> The --use-syslog option no longer works on a separate facility. This
option was configured and working fine using facility 'local1' on my machine
with ntop 2.2c. Initially I had a problem with the -L option that was hard
coded in the init.d script, but this has been repaired (see separate init.d
issues below). If using -L it processes normally to the daemon facility.
With --use-syslog=local1 only the following is being inserted in
/var/log/messages: "Processing file /etc/ntop.conf for parameters...",
followed by this message AGAIN (strange), followed by "ntop startup
succeeded". When ntop is shutdown "ntop shutdown succeeded" is logged.
Facility local1.* is configured in /etc/syslog.conf to go to file
/var/log/ntop. The file is not being created when ntop is started.
Touching the file manually and changing ownership to ntop does not help
either (was not required for 2.2c). Looking at the ntop web configuration
screen shows that the option is in fact being parsed and the option line
shows that facility local1 should be in use. A very interesting aspect is
the fact that the ntop web interface sees the log activity. My guess is
that the log data is being held in memory. lsof of the ntop process shows
an open write only pipe. Further testing by hard coding --use-syslog=local1
in the init script and removing it from /etc/ntop.conf does not help either.
<snip/>
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
