From owner-freebsd-questions@FreeBSD.ORG Thu Feb 19 09:24:13 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDCCE16A4CE for ; Thu, 19 Feb 2004 09:24:13 -0800 (PST) Received: from clanbuckbuck.org (c-24-17-98-189.client.comcast.net [24.17.98.189]) by mx1.FreeBSD.org (Postfix) with SMTP id A1B5B43D1D for ; Thu, 19 Feb 2004 09:24:13 -0800 (PST) (envelope-from ryallsd@datasphereweb.com) Received: (qmail 5021 invoked from network); 19 Feb 2004 17:24:12 -0000 Received: from unknown (HELO RYALLS1) (131.107.3.74) by c-24-17-98-189.client.comcast.net with SMTP; 19 Feb 2004 17:24:12 -0000 From: "Derrick Ryalls" To: , Date: Thu, 19 Feb 2004 09:24:04 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <005101c3f6ef$54615f30$0701a8c0@darryl> Subject: RE: crontab question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 17:24:14 -0000 > Greetings, > I am running 5.1-release. I created the file=20 > /var/cron/tabs/root . It is owner root, group wheel.=20 > permissions are -rw------- >=20 > I have the following entry in the file root >=20 > 0 22 2-31 * * /usr/local/bin/rsync -av /dept2/Marketing/=20 > /data/Marketing > 2>&1 /r > oot/rsync.log >=20 > Of course the line above is all on one line. >=20 > Well, this command did not run last night. No=20 > /root/rsync.log file was created. No email was generated. Zip. >=20 > what did I screw up to prevent cron from running the command ? >=20 As far as I know, you should never manually create a crontab file. = Normal users should just type crontab -e on a command line for scheduling. The same might apply to root, never tried personally. One sure fire way to = get it working is to add your above line to /etc/crontab with root in the = user column. This is not normally recommanded, so you might try doing = crontab -e as root first.