- --On February 13, 2008 9:50:21 AM -0800 Mark Duling <[EMAIL PROTECTED]> wrote:

|
|
| >> Hi Mark,
|
| | Hello,
| |
| | When I start nfsen (I have the latest version of nfsen and nfdump with
| | -enable-nfprofile) and nfcapd is crashing for me at startup before any
| | information can be logged to syslog as far as I can tell.  RRD is linked
|
| >> crashing?? I'm not aware of any nfcapd crashes. What system/OS are you 
using?
| >> btw. nfcapd is not related to rrd or Perl, and can be independently 
started.
|
| >> How does your nfsen.conf file looks like?
|
| Hi Peter,
|
| I'm on OS X.  It weird because nfcapd starts on its own ok.  But it won't 
start via nfsen.  My nfsen.conf has PREFIX set to
| the right path.  I don't get it either.  The "crash" is reported through OS 
X's reporting facility.  Perhaps it is some weird
| platform issue.  I'll investigate more.

>> Entire NfSen itself does not start properly on MacOSX as Apple's Perl does 
>> not support
>> dropping user privileges. You need to check for a 3rd party Perl allowing 
>> these
>> privileges settings:

>>    $( = $www_gid;
>>    $) = "$www_gid $(";

>>    $> = $nf_uid;

>> Not sure, but fin's Perl might .. unsure ..

Ah, I forgot to mention that I thought I'd worked around that by commenting out 
these lines in nfsend:

=======
if ( !NfSen::DropPriv($NfConf::USER) ) {
die "$Log::ERROR\n";
}
=======

Then I changed NfSenRC.pm from this:

system "$NfConf::BINDIR/nfsend";

to this:

system "/usr/bin/su netflow -c $NfConf::BINDIR/nfsend";

That was the attempt to work around the droppriv deficiency in OS X perl.  
Sorry I didn't mention that.  I may have gone beyond what you can support.

Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss

Reply via email to