On 09/21/2016 10:45 AM, Tom Horsley wrote: > On Wed, 21 Sep 2016 19:26:18 +0200 > Patrick Dupre wrote: > >> Why give up this logic? > > Because my machine is never turned off, and anacron has the > uncanny ability to make things run at the most inconvenient possible > times to interfere with things I'm trying to do. You do know you can modify the "START_HOURS_RANGE=" parameter in /etc/anacrontab to tell anacron when it is permitted to run things, right? By default it's set to "3-22" permitting things to be run between 3 a.m. and 10 p.m. If that's inconvenient, then perhaps changing it to START_HOURS_RANGE=2-7 (permit runs between 2 and 7 a.m.) might work. > Cron runs thing when I want them to run. Well, yes, of course. Remember that anacron is really intended to do "housekeeping" stuff like rebuilding the man pages, updating the locate databases and such when the machine isn't busy and to ensure they get done even if the power has been off for a while. It's up to you to tell it when the machine "isn't going to be busy". I agree that the defaults of 0300 through 2200 is likely to include the times the machine is in use, but it's easy enough to alter. If you want to disable anacron but leave it installed, just echo "0anacron" >>/etc/cron.hourly/jobs.deny That prevents anacron from running (anacron is launched by cron every hour and that tells cron NOT to run it) ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - A friend said he climbed to the top of Mount Rainier. My view is - - that if there's no elevator, it must not be that interesting. - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
