On Mon, Feb 01, 2010 at 12:53:24AM +0100, Ingo Schwarze wrote: > Joakim Aronius wrote on Fri, Jan 29, 2010 at 09:32:05AM +0100: > > * Ingo Schwarze (schwa...@usta.de) wrote: > > >> situation, so i consider tedu@'s question unanswered. I'm not even sure > >> there is a good solution at all: Jan Stary and Jonathan Thornburg have > >> presented strong arguments indicating that "run it manually at the time > >> you want it" might be the best answer. > > > What about a new script that runs daily/weekly/monthly as needed to make > > it a bit simpler. The user would then not have to keep track of which > > script to run. This script could be called manually or the user could > > ad it in cron or shutdown script as it suits the user/machine. > > Simplifying a bit: Run weekly(8) and monthly(8) from daily(8) instead of > from cron(8), but only when the last run is at least a week or a month > ago, respectively. This is similar in spirit to the way security(8) > is run. > > Main advantage: When your notebook is in use every N-th night, > the weekly(8) mean period decreases from 7*N days to 7+(N-1)/2 days. > > Bonus: Get rid of duplicate functions in weekly(8) and monthly(8). > > Side effect: daily(8), weekly(8) and monthly(8) run one after the other, > not in intervals of two hours. In some setups, this might be a bonus, > in some others, an inconvenience. > > Thoughts?
but what if your machine never runs daily(8) because it's not on at the right time? isn't that the original issue? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
