* correct init
@ 2019-05-16 15:33 Jeff
2019-05-16 15:52 ` Jeff
0 siblings, 1 reply; 2+ messages in thread
From: Jeff @ 2019-05-16 15:33 UTC (permalink / raw)
To: supervision
new postulation:
process #1 should not rely on conditions that it has not previously
ascertained to be true (eg by setting something up by itself, so it
exists and is safe to use/rely on it).
sounds self-evident ? sadly many inits do not comply with that
postulation, a well known example that comes immediatly to mind
is the poorly designed/though out SysV init itself.
the poor crap relies on the initctl fifo for ipc, how dumb can one be ?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: correct init
2019-05-16 15:33 correct init Jeff
@ 2019-05-16 15:52 ` Jeff
0 siblings, 0 replies; 2+ messages in thread
From: Jeff @ 2019-05-16 15:52 UTC (permalink / raw)
To: supervision
> process #1 should not rely on conditions that it has not previously
> ascertained to be true (eg by setting something up by itself, so it
> exists and is safe to use/rely on it).
> sounds self-evident ? sadly many inits do not comply with that
> postulation, a well known example that comes immediatly to mind
> is the poorly designed/though out SysV init itself.
it also relies on syslog for logging, though it cannot ensure someone
listens to /dev/log and processes the log messages.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-16 15:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-16 15:33 correct init Jeff
2019-05-16 15:52 ` Jeff
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).