4 ms·
Funny part to that, was on a project with multiple teams with multiple crontabs. Each team took that advice to heart for some jobs. Sadly, we had too many Hit
by protomyth 12y ago
Funny part to that, was on a project with multiple teams with multiple crontabs. Each team took that advice to heart for some jobs. Sadly, we had too many Hitchhiker fans and :42 became a bit too common.
- kijin 12y agoUse the following shell command to decide when to run cron jobs. echo $((RANDOM % 60)) It's not a CSPRNG, but good enough for this kind of load balancing!
- cperciva 12y agoOr schedule your cron job for :00, but add "sleep `jot -r 1 0 3600` &&" to the start of the command. (jot is a BSDism, but I assume you can do the same with GNU seq.)
- junkblocker 12y agosleep $[RANDOM/3600] works everywhere without requiring jot/seq etc. on BSD/Mac/Linux.
- cperciva 12y agos/\//%/ I assume?
- deleted 12y ago[deleted]
- junkblocker 12y agoOops s/\//\\%/ yeah. sleep $[RANDOM\%3600]
- hjnilsson 12y agoThat will be a number between 1 and 10 ($RANDOM only goes to 32767), sleep $[RANDOM/10] would be better. :) This might be platform dependent though, I can't find any standard RAND_MAX in bash so it's difficult to make this work everywhere.
- lloeki 12y agoThis works in (da)sh (tweak 2 and 65536 if needed): sleep $(( 0x$(xxd -l2 -p /dev/random) * 3600 / 65536 ))
- JoachimSchipper 12y agoDon't use that for hourly jobs, though - things are liable to break when you randomly run a command at, say, 12:59 and 13:00.
- cperciva 12y agoRight, I usually do that for my daily jobs.
- rlpb 12y agoThis is a pain when deciphering a series of events later, though, because you don't know when a particular job was supposed to start. I'd prefer the delay to be stable on a per-host basis.
- protomyth 12y agoWe just went with a single group text file with all the jobs and which ones could be spread out. Saves the programming and gives the sys admins / DBAs an idea what goes when.