Tilted Forum Project Discussion Community - View Single Post

skaven · 11-22-2004, 06:05 PM

I set up a cronjob to automagically record Futurized Radio every monday on www.protonradio.com. Here's the line in my crontab:

55 19 * * mon cd "/tool/storage/MP3s/Electronica/Breaks/Futurized Radio" && /tool/box/bin/streamripper http://64.236.34.196:80/stream/1041 -s -l 8400 >/dev/null 2>&1 &

It works quite well, except that at 7:55 every monday, *TWO* of these jobs spawn in rapid-fire succession (so fast, in fact, that the PIDs look like this:

PIDn /bin/sh #1
PIDn+1 /bin/sh #2
PIDn+2 streamripper #1
PIDn+3 streamripper #2

I've already checked, double-checked, and triple-checked that I don't have any other crontabs set up. Besides, both of the streamripper processes run under my user id. The only thing I can think of is that I've somehow botched the timing portion of the crontab, causing cron to think it's supposed to run that command twice (once for it being monday, and again for it being 7:55, for example). It also might be that I'm backgrounding the process...

Anybody had cron do weird stuff like this? Any suggestions?

Thanks!

11-22-2004, 06:05 PM	#1 (permalink)
skaven Insane Location: Austin, TX	cronjob on my server acting weird I set up a cronjob to automagically record Futurized Radio every monday on www.protonradio.com. Here's the line in my crontab: 55 19 * * mon cd "/tool/storage/MP3s/Electronica/Breaks/Futurized Radio" && /tool/box/bin/streamripper http://64.236.34.196:80/stream/1041 -s -l 8400 >/dev/null 2>&1 & It works quite well, except that at 7:55 every monday, TWO of these jobs spawn in rapid-fire succession (so fast, in fact, that the PIDs look like this: PIDn /bin/sh #1 PIDn+1 /bin/sh #2 PIDn+2 streamripper #1 PIDn+3 streamripper #2 I've already checked, double-checked, and triple-checked that I don't have any other crontabs set up. Besides, both of the streamripper processes run under my user id. The only thing I can think of is that I've somehow botched the timing portion of the crontab, causing cron to think it's supposed to run that command twice (once for it being monday, and again for it being 7:55, for example). It also might be that I'm backgrounding the process... Anybody had cron do weird stuff like this? Any suggestions? Thanks! Last edited by skaven; 11-22-2004 at 06:07 PM..