Date: Sun, 13 Oct 1996 03:15:10 +-200 From: David Stickney <david@wvb.gomel.by> To: "'FBSD ISP'" <freebsd-isp@freebsd.org> Subject: FW: CRON freeking out on UUCICO, little voices crying "there is an answer, yeah, just jump, jump, open the window and..." Message-ID: <01BBB8B4.BF1885A0@david.wvb.gomel.by>
next in thread | raw e-mail | index | archive | help
From: David Stickney Sent: Saturday, October 12, 1996 05:07 PM To: 'FBSD ISP'; 'Unibel.by' Subject: CRON freeking out on UUCICO, little voices crying "there is an answer, yeah, just jump, jump, open the window and..." Hi, Has cron ever driven anyone to suicide? I have the entries /etc/crontab * 6,8,10,12,14,16,18,20, * * * root /usr/libexec/uucp/uucico -sbrc -r1 -x all -f call every 2 hours from 6 to 8, my email host, full debuging, even with an empty spool I stuck it in there yesterday, at about 2, then went home. I come 5 hours later to learn my machine called long distance 180 times to get my mail. I spent all day trying different configs, command line options thinking that UUCICO was the problem. UUCICO exits cleanly, leaves a call completed in the status file, calls uuxqt, and exits, uuxqt does the same. at this point uustat -p shows no jobs, ps -x shows only one cron. Then the fun starts, a second copy of cron runs, locks my modem and starts to dial again, and again, and again, regardless of the system status. uucico is the only program that cron does this to everything else works fine. If I take out the -f (force the call), set the failed call wait period to 5 minutes, it will try to dial every 20-30 seconds, and uucico will allow it to dial only after the five minutes have passed. Running this from a script works fine, the sys status file is updated and everything is cool. But that means I have to be here if everyone wants to get their mail or let someone play with hours of my work. Has anyone dealt with this, had a similiar problem know a fix? I was going to just kill the process after the call, but it leaves the spool dirty. I have worked hours try to track down my problem and it's cron, or maybe it's just me, yeah,,, the window,, Yeah...soo easy.. ;] Thanks for reading this, Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01BBB8B4.BF1885A0>