Story
Is it time to fork Debian?Preview
History
2014-10-20 02:18
Some daemons are built to recover from crashes and restart their own worker processes. For example, Apache's main pid is mainly in charge of spawning new child processes to do the actual work. The children can even be configured to terminate themselves after serving X number of requests.
However, some daemons, such as mysql end up relying on a shell script to do this task. I've always thought of the mysql_safe script as being an ugly hack. Wouldn't a real program be a better fit for this? And if you make a generic enough service monitor, couldn't you use it for more than just one program?
The traditional inetd process is another example. The post-fork method of operation is just too slow for modern tasks such as web page serving. But systemd does have some interesting ideas on how to fix it.
However, some daemons, such as mysql end up relying on a shell script to do this task. I've always thought of the mysql_safe script as being an ugly hack. Wouldn't a real program be a better fit for this? And if you make a generic enough service monitor, couldn't you use it for more than just one program?
The traditional inetd process is another example. The post-fork method of operation is just too slow for modern tasks such as web page serving. But systemd does have some interesting ideas on how to fix it.
2014-10-20 02:19
Some daemons are built to recover from crashes and restart their own worker processes. For example, Apache's main pid is mainly in charge of spawning new child processes to do the actual work. The children can even be configured to terminate themselves after serving X number of requests.
However, some daemons, such as mysql end up relying on a shell script to do this task. I've always thought of the mysqld_safe script as being an ugly hack. Wouldn't a real program be a better fit for this? And if you make a generic enough service monitor, couldn't you use it for more than just one program?
The traditional inetd process is another example. The post-fork method of operation is just too slow for modern tasks such as web page serving. But systemd does have some interesting ideas on how to fix it.
However, some daemons, such as mysql end up relying on a shell script to do this task. I've always thought of the mysqld_safe script as being an ugly hack. Wouldn't a real program be a better fit for this? And if you make a generic enough service monitor, couldn't you use it for more than just one program?
The traditional inetd process is another example. The post-fork method of operation is just too slow for modern tasks such as web page serving. But systemd does have some interesting ideas on how to fix it.
Moderation
Time | Reason | Points | Voter |
---|---|---|---|
2014-10-20 03:32 | Insightful | +1 | evilviper@pipedot.org |
Junk Status
Not marked as junk