> I still fail to see how at/anacron/cron and inetd and init are
> variations of the same task, other than the most vague idea that "they
> are all ways of starting programs/services." (so is the command line...
> are we somehow going to move that into upstart too?) Their functions
> are quite different.
Other than inetd, they all start tasks at different times (startup and
every 3pm, etc). All of them need to sanatize the shell, report on
failure, etc.
Of course I'd just write a program called sanatize - then I could
include it at the top of my scripts if needed. As you said I need
that from the CLI at times too.
To report on the status, I'd probably create a daemon. I'd write to
that daemon's socket on start up and completion. Any program could
register with it. If I tell that daemon my pid, it could check if
I've crashed from time to time too. Or something.
There is still that pid start up race condition, but I've never been
hit with that in practice.
Received on Sat Jan 6 13:59:33 2007
This archive was generated by hypermail 2.1.8 : Sat Jan 06 2007 - 13:59:39 CST