3 ms·
This comment thread seems to be the 2-minutes-hate for systemd, with mostly predictable results. But the actual news seems to be that Busybox removed the use o
by teddyh 11y ago
This comment thread seems to be the 2-minutes-hate for systemd, with mostly predictable results. But the actual news seems to be that Busybox removed the use of the systemd notify system which lets systemd know that the service has indeed started and it’s OK to start other processes which depend on it. This is no great thing – the normal and traditional Unix way of daemons is for a program to fork, where the fork continues to be the actual daemon, and the original process exits. Systemd can detect this exiting of the started process, and will take that as the signal that the daemon is ready, so there is no need for the notifying function in this case.
- JdeBP 11y agoThat is wrong in three ways. * That's not what the removed code was doing at all. * That's a 1980s idea of "normal". Forking is something that has been gradually disappearing as standard practice for daemons for the past 16 years, as can be seen from the large number of daemons that now have "don't fork" modes, as compared to the number in the middle 1990s. The idea that daemons fork as some sort of standard practice was the mainstream thinking then, but it is not now. * Most programs in the wild do not correctly speak the forking readiness protocol, in part because those programs are not forking as a readiness protocol in the first place. Many people, in particular those involved in the Debian Technical Committee hoo-hah a while back, considered the opposite of what you claim to be actually true. There is no need for the flawed, bodged, and in practice broken forking readiness protocol when one has a proper readiness notification protocol. http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/unix-daemon-readiness-protocol-problems.html#NooneSpeaksForking http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/un...
- teddyh 11y ago> * That's not what the removed code was doing at all. All right, what was the removed code doing? > * That's a 1980s idea of "normal". That’s why I called it “normal and traditional”. > * Most programs in the wild do not correctly speak the forking readiness protocol True enough. But for practical purposes, it’s mostly good enough. And I’d think that it doesn’t matter that much for people running BusyBox with sysvinit.