Date: Wed, 9 Aug 2000 12:50:03 -0700 (PDT) From: Brett Glass <brett@lariat.org> To: freebsd-bugs@FreeBSD.org Subject: Re: conf/20498: All FreeBSD systems trigger massive late-night activity at the same times Message-ID: <200008091950.MAA34226@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR conf/20498; it has been noted by GNATS. From: Brett Glass <brett@lariat.org> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: conf/20498: All FreeBSD systems trigger massive late-night activity at the same times Date: Wed, 09 Aug 2000 13:45:56 -0600 At 05:56 AM 8/9/2000, Neil Blakey-Milner wrote: >This is a system's administrator's job, surely? Sysadmins already have a lot to do manually installing the OS. Why make their lives harder? >A gratuitous change >like this by default will confuse and probably irritate many. It's not gratuitous. It does not make sense to have EVERY FreeBSD server in the same time zone suddenly thrash at the same time! >And I >personally wouldn't like to have to document it. It'd be easy. Simply say that the scripts do a random delay (which could, perhaps, be turned off via a variable in rc.conf) and then continue. >One possible solution is to add a 000.time-wait.sh script to your >periodic/daily directory, which has "perl -e 'sleep int(rand(180))' in >it (overkill, I know). > >You can change '180' to get a number from a variable in periodic.conf, >for example. It would default to 0, or something. If you don't want >_each_ invocation randmomized, then make the number you get from a >variable in periodic.conf be the exact offset. Why not put that random delay right in the daily/weekly/monthly scripts? Or in /etc/crontab, where it's easy to spot? --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008091950.MAA34226>