nikmit has asked for the wisdom of the Perl Monks concerning the following question:

This one does not seem like something I can easily google, so I'm hoping for the monks' expert opinion :)

I have a script which needs to run constantly. Writing a proper .service file for it and handling it via systemd seemed like the proper thing to do, but when I got to watchdog and sd_notify it got fairly complicated and I found myself wondering if it is worth the effort... An obvious alternative is to manage it via Monit, which we are already using for other stuff. My current plan is to run it as a service, but don't enable watchdog for it and don't send any notifies to systemd - manage uptime and restarts with Monit. Am I cutting corners I shouldn't?
  • Comment on Monitoring and restarting a proces via systemd vs monit

Replies are listed 'Best First'.
Re: Monitoring and restarting a proces via systemd vs monit
by RonW (Parson) on Jan 26, 2016 at 17:50 UTC
[reply]
Re: Monitoring and restarting a proces via systemd vs monit
by crusty_collins (Friar) on Jan 26, 2016 at 14:31 UTC
    I think this is the wrong forum for this question
    "We can't all be happy, we can't all be rich, we can't all be lucky – and it would be so much less fun if we were. There must be the dark background to show up the bright colours." Jean Rhys (1890-1979)
[reply]
      Not really. Unlike places like stack-exchange, PerlMonks does have a long history of (within reason) off topic discussions. Historically, the convention/polite thing has been to put an 'OT' in the title.
[reply]
Re: Monitoring and restarting a proces via systemd vs monit
by Anonymous Monk on Jan 27, 2016 at 06:30 UTC

    Hi,

    If you are already doing similar stuff, do it the same way.

    It's one less thing for all the other staff to learn.

    J.C.

[reply]

Back to Seekers of Perl Wisdom