From owner-freebsd-hackers Tue May 21 08:55:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA04504 for hackers-outgoing; Tue, 21 May 1996 08:55:14 -0700 (PDT) Received: from kilgour.nething.com (kilgour.nething.com [204.253.210.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA04495 for ; Tue, 21 May 1996 08:55:08 -0700 (PDT) Received: from randy.nething.com (randy.nething.com [204.253.210.83]) by kilgour.nething.com (8.6.11/8.6.9) with SMTP id KAA12415; Tue, 21 May 1996 10:53:54 -0500 Date: Tue, 21 May 1996 10:53:54 -0500 Message-Id: <2.2.16.19960521105252.264755cc@nething.com> X-Sender: rberndt@nething.com X-Mailer: Windows Eudora Pro Version 2.2 (16) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "Andrew N. Edmond" , hackers@freefall.freebsd.org From: Randy Berndt Subject: Cron Loves Me Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I am getting from my cron daemon (every FIVE minutes!), the following >message: > > From root@shaman.lycaeum.org Mon May 20 23:37:44 1996 > Date: Mon, 20 May 1996 23:35:00 -0600 (MDT) > From: Cron Daemon > To: root@shaman.lycaeum.org > Subject: Cron root /usr/libexec/atrun > > root: not found > >which, in the tradition of UNIX, is pretty vague. Speaking from PAINFUL personal experience: You have somehow gotten the 'atrun' line from the SYSTEM cron file (stored in /etc/crontab) inserted into roots PERSONAL cron file (by doing 'crontab -e' as root probably). The system file has an additional parameter after the 5th field, the user to run as. Each persons file only runs as themselves, so they don't need the user parameter. To modify SYSTEM tasks, just edit /etc/crontab. The systems sees the modification time change (I think that's the trigger), and reloads the data. Randy Berndt ---------------------------------- AOS/VS, FreeBSD, DOS: I'm caught in a maze of twisty little command interpreters, all different.