in reply to Re: Perl Daemons
in thread Perl Daemons

Maybe one should use another server monitoring software ;.)

At my company we are using mon, a fantastic peace of software to monitor more than fifty devices.

Mon is a perl script (sic!) and the last time I bootet the server was January 1 this year, because we had to take away the power of the whole server room. Before that the server was running for more than 400 days and mon.pl is only being restartet when there are any config changes - I think I should even be able to reload the config with a SIG HUP, but didn't test it already.

The server is running SuSE Linux 8.0 with a 2.4 kernel.

Therefore I do not see any reason to restart a good written piece of perl daemon software just to avoid any potential trouble!

Cheers Roland

Replies are listed 'Best First'.
Re^3: Perl Daemons
by paulbort (Hermit) on Jul 29, 2004 at 15:26 UTC
    I'm sure that the OP can use care and write a solid, non-leaking daemon that would run for years. I did not mean to disparage OP's daemon, coding, or any monitoring software.

    I did mean that there are millions of lines of very clever code holding up that daemon, and it is impractical to test that code for months of constant operation. So as a precaution, monthly server restarts will do two things:
    1. Prevent any long-term leakage problems from rearing their ugly heads
    2. Catch any configuration changes that might have been made in the preceding month that would prevent the server from returning to normal operation. A failed restart at the beginning of a maintenance window is much easier to deal with than a failed restart after a move or extended power outage.

    --
    Spring: Forces, Coiled Again!
[reply]

In Section Seekers of Perl Wisdom