From owner-freebsd-isp Mon Nov 18 06:17:26 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16262 for isp-outgoing; Mon, 18 Nov 1996 06:17:26 -0800 (PST) Received: from unibel.by (alice.unibel.by [195.50.0.195]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16038 for ; Mon, 18 Nov 1996 06:15:58 -0800 (PST) Received: from brc.minsk.by (brc.minsk.by [193.232.92.36]) by unibel.by (8.8.2/8.8.2) with SMTP id NAA16632 for ; Mon, 18 Nov 1996 13:18:45 +0200 (EET) Received: by brc.minsk.by (sendmail 8.6.6/8.6.8) id m0vPRWI-001C5wC; Mon, 18 Nov 96 13:05 EET Received: from david.wvb.gomel.by (david [150.97.0.2]) by wvb.gomel.by (8.7.5/8.7.3) with SMTP id BAA03250 for ; Mon, 18 Nov 1996 01:04:52 +0200 (EET) Received: by david.wvb.gomel.by with Microsoft Mail id <01BBB8B4.BF1885A0@david.wvb.gomel.by>; Sun, 13 Oct 1996 03:15:12 +-200 Message-ID: <01BBB8B4.BF1885A0@david.wvb.gomel.by> From: David Stickney To: "'FBSD ISP'" Subject: FW: CRON freeking out on UUCICO, little voices crying "there is an answer, yeah, just jump, jump, open the window and..." Date: Sun, 13 Oct 1996 03:15:10 +-200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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=20 /etc/crontab=20 * 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.=20 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.. ;] =20 Thanks for reading this, Dave