From owner-freebsd-current Tue May 2 21:25:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA28444 for current-outgoing; Tue, 2 May 1995 21:25:28 -0700 Received: from pluto.ops.NeoSoft.com (pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA28436 for ; Tue, 2 May 1995 21:25:24 -0700 Received: from metal.ops.neosoft.com (root@glenn-slip54.nmt.edu [129.138.5.154]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id XAA06085; Tue, 2 May 1995 23:24:48 -0500 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id WAA01623; Tue, 2 May 1995 22:24:44 -0600 From: Scott Mace Message-Id: <199505030424.WAA01623@metal.ops.neosoft.com> Subject: Re: problems with cron... To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 2 May 1995 22:24:43 -0600 (MDT) Cc: current@FreeBSD.org In-Reply-To: <199505030419.VAA03841@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 2, 95 09:19:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 979 Sender: current-owner@FreeBSD.org Precedence: bulk bingo... thats it... I've always done: crontab /etc/crontab to install the new crontab, and totally forgot that it actually parses /etc/crontab.... ok, I feel _REAL_ smart right now :-) Scott > > > > > > > Can someone test to see if crontab -e works? > > > > I did a > > > > crontab -e > > * * * * * root /bin/ls > > Now I know what your problem is, crontab -e when logged in as root > edit's /var/cron/tabs/root. Files in /var/cron *DO NOT* take a > user name field!! Only /etc/crontab does, and you use vi or any > other editor to change it, not crontab -e!!!! > > > and then: > > > > crontab -e > > > > and deleted it > > > > but it kept on running once a minute > > CHeck that /var/cron/tabs/root is empty, rm it since you probably > don't want one there anyway, kill and restart cron. > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD >