Re: Starting sysmon from /etc/inittab
Jared Mauch <[email protected]> Sat, 29 Nov 2003 23:45:18 -0500
| Newsgroups | gmane.comp.monitoring.sysmon.help |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Nov 29, 2003 at 09:10:05PM -0600, Jim Vaughan wrote: > Hello all, > > When I start sysmond via an entry in /etc/inittab like this: > > sm:3:respawn:/usr/local/bin/sysmond > > init tells me that sysmond is respawning too fast. I assume that this is > because sysmond is forking (a) child process(es), or something like that. Yes, this is correct. > When I start sysmond from /etc/inittab with the "-d" option like this: > > sm:3:respawn:/usr/local/bin/sysmond -d > > all is well, and when I kill the sysmond process, it promptly respawns. > > What am I missing out on by using the "-d" option? If I should NOT be using > the "-d", then is there a way to make sysmond behave correctly under init? This is what you want to use, the -d option. It just tells sysmon to not fork, that's it. - jared > > Thanks, JV. > > --- > Jim Vaughan - Mead, NE, USA > [email protected] > http://www.jimvaughan.com > ftp://ftp.jimvaughan.com > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.545 / Virus Database: 339 - Release Date: 11/27/2003 > > _______________________________________________ > Sysmon-help mailing list > Sysmon-help-li9M/[email protected] > https://puck.nether.net/mailman/listinfo/sysmon-help -- Jared Mauch | pgp key available via finger from jared-li9M/[email protected] clue++; | http://puck.nether.net/~jared/ My statements are only mine.