Thanks Steve for the heads up on the proper place to post this and that
you've already submitted a fix. I just responded back to the list because
this was the original posting place and wanted to make sure anyone else
performing this fix until your patch goes through doesn't fall into the trap
of putting the switches after the ntop.conf file.
____________________________
Matt Ausmus
Network Administrator
Chapman University
635 West Palm Street
Orange, CA 92868
(714)628-2738
mausmus@xxxxxxxxxxx
"You can lead a horse to water, but if you can get him to float on his back,
you've got something."
-HARTLEY'S FIRST LAW
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf
Of centos-request@xxxxxxxxxx
Sent: Friday, December 11, 2009 9:00 AM
To: centos@xxxxxxxxxx
Subject: CentOS Digest, Vol 59, Issue 11
Message: 24
Date: Thu, 10 Dec 2009 15:00:54 -0500
From: Steve Huff <shuff@xxxxxxxxx>
Subject: Re: ntop from rpmforge
To: CentOS mailing list <centos@xxxxxxxxxx>
Message-ID: <A0BA4C1D-A27C-475A-8489-54E009FABE44@xxxxxxxxx>
Content-Type: text/plain; charset="windows-1252"
On Dec 10, 2009, at 1:39 PM, Ausmus, Matt wrote:
> Anywho, I wanted to post this response to a thread that was created
> back in November 2008 about the ntop daemon failing to start. I?m
> currently setting up ntop as a NetFlow & SFlow collector and came
> across the issue. A quick refresher, the init script for ntop has
> an issue where it can?t parse the ntop.conf file correctly if
> switches are entered before the ?@/etc/ntop.conf?. The suggested
> work around was to move the ?-d ?L? switches from in front of the ?@/
> etc/ntop.conf? and put them behind it. This is definitely the fix.
> There is a caveat to that and I haven?t found anyone that has
> mentioned it so I thought I would. According to the documentation,
> if you add the switches after the ?@/etc/ntop.conf? those will
> override the configurations in the ntop.conf file. While this isn?t
> an issue with the ?-d? option, if you decide to use a custom syslog
> level and add it to the conf file, the ?-L? switch after the conf
> file will override your custom log facility. In my init file I left
> the ?-d? but removed the ?-L? expecting me to put my own syslog
> entry in the conf file.
thanks for the report! the appropriate place to report such issues is
the RPMforge users' list, <users@xxxxxxxxxxxxxxxxxx>.
i've committed a fix; once the package is rebuilt, it should appear in
the repository.
-steve
--
If this were played upon a stage now, I could condemn it as an
improbable fiction. - Fabian, Twelfth Night, III,v
http://five.sentenc.es
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url :
http://lists.centos.org/pipermail/centos/attachments/20091210/5c6682eb/attac
hment-0001.bin
***
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
