Re: /var/run/

> init: starts programs at startup. Backgrounds them (okay... they have
> to background themselves...) and they write to logs (usually). Programs
> should not accept interactive input. (with a few possible exceptions.)
> (BTW, I've heard enough intelligent replies here to agree that something
> better could replace init.)
>
> at/anacron/cron: start programs at specified times. Program results are
> emailed to user who requested the program to run. Programs must run
> without interactive input.

Except I need something to query if I program is running/ran properly.
 I regularly end up writing cron jobs, and then more cron jobs
(usually on another machine...) to make sure the first actually ran.

Right now I'm wrestling with a script which works great on the
console, but init won't run it.

I also end up copy and pasting the same dozen lines into each of my
scripts - lockfile-progs to ensure only one copy will run at a time.

I'm not arguing for upstart (or any monolithic program). But I am
arguing for a common framework for the feature they're talking about.

Of course for most of these things I've built up a shell toolbox to
solve them, so its not too hard these days.

> I might call it sanitize, but that's just nitpicking. ;-)

Alls I know is that I prefer to sanatize stuff.
Received on Sat Jan 6 15:43:59 2007