Hi Dave, > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Dave Shield > Sent: Wednesday, July 26, 2006 5:12 PM > To: vic > Cc: [email protected] > Subject: Re: Issue when enabling SNMPD (w/ pr & dskTables support) at an > > early boot level
> I presume that syslog isn't running at this point (which is the > default logging mechanism). Nope. > Note that there shouldn't be a space between 'L' and 'f'. > Try "-Lf /var/log/file" > It might also be worth running "snmpd -f -Le" > That will probably temporarily block whatever comes after, but it > might at least let you see any error messages. Ok. I've tried the "-f Le" call. The result is not good. I've gotten a "segfault" as snmpd dies. And ofcourse, nothing is logged. With this, I'm inclined to think that snmpd maybe looking for some environment variables/values/or something similar which may not yet be available at that very early stage in boot-up. And at that stage, I only made sure that libraries (via ld.so.cache) can be located by programs getting executed. And yep, paths are likewise properly mapped also. What's really puzzling is why disk monitoring in config results to this crash. Below are the lines that did it: Disk / 10% Disk /Home/data 5% Disk /Home/updates 3% (once more, having above lines commented out, snmpd runs at the early boot stage. And after call to /sbin/init, above disk lines does not crash snmpd). Thanks and best regards, Vic ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
