On Tue, May 27, 2008 at 01:09:49PM -0700, Jordan Brown wrote: > Nicolas Williams wrote: > >cron does not, however, keep track of past job runs, and this is lame: > >you must check your e-mail. One potentially quite useful improvement to > >cron might be to track failure rates per-job and recent history. > > So you mean that perhaps each cron job should have a log file showing > the results of its previous runs? > > Er... like /var/svc/log/*.log?
Sortof. I guess the point is that "gee, you get that from SMF for free," but I don't argue against re-using SMF framework. Really, different FMRI type != so different from SMF that you can't re-use any part of it. > >Another potentially quite useful improvement to cron might be job > >dependencies (e.g., "user is logged in on console," "user is logged in," > >"Kerberos credentials are available," ...). > > Hmm. That starts to hint at something I was thinking about but didn't > want to get into: using something SMF-like to manage your desktop > sessions. Why is "if user is logged in" more closely tied to cron jobs > than it is to general services? I would, eventually, like to see > something a lot like SMF used to control all of the little > mostly-background doodads that run as part of my desktop session, > possibly including cron-like time-based operations... but not today. I think you'll want a per-user repository (stored in $HOME/.something/ by default, + a per-session running snapshot (stored in $TMPDIR/$SessID, say). Nico --
