Tag Info

New answers tagged

0

Well, that is one of the main reason, why debian is moving to systemd. sysvinit (/etc/init.d) is not able to detect, if a service is down/not responding. This means you have to monitor these services and escalate if a service won’t do his job anymore. probably the easiest thing to do would be to migrate to another daemonhandler like systemd (default in ...


2

You could add it to /etc/inittab with respawn: d1:2345:respawn:/path/to/your/first_daemon arg1 arg2 d2:2345:respawn:/path/to/your/second_daemon arg1 arg2 It's a dirty hack, but I've used it succesfully in the past on older sysv-init systems.


0

Debian will eventually have systemd, so this is the way to do it on a Linux system which uses systemd (and many do already; you might consider switching distributions). Systemd can handle keeping the service alive for you automatically; no other tools are required. Simply make sure that Restart=always is set in the service file's [Service] section. # vi ...


0

The standard approach for me is to use the Monit utility for this. I can't quite tell from your description if you've written something like Monit and are trying to make sure it's running, or if you need something to watch the daemon you've created.


0

Best practice is to ensure that your daemons DO NOT STOP in the first place. Failing that you might want to have a look at DJB's daemontools


0

Haven't heard about a splash screen option but have a look at this Hope this helps.


0

I know this is an old question, but I'm posting in case anyone else is looking for a better/different answer. I've been having a similar problem, but when installing upgrades. Ours takes a long time to start as it is part of a Galera cluster and needs to copy over what it missed while it was down. To start run: MYSQLD_STARTUP_TIMEOUT=900 /etc/init.d/mysql ...



Top 50 recent answers are included