From owner-freebsd-questions@FreeBSD.ORG Thu Feb 19 09:29:42 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 A6E3716A4CE for ; Thu, 19 Feb 2004 09:29:42 -0800 (PST) Received: from gabby.gsicomp.on.ca (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [67.60.54.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5768343D1D for ; Thu, 19 Feb 2004 09:29:42 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by gabby.gsicomp.on.ca (8.12.9p2/8.12.9) with ESMTP id i1JHUYpU016619; Thu, 19 Feb 2004 12:30:34 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <000f01c3f70d$855fa7e0$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: , References: <005101c3f6ef$54615f30$0701a8c0@darryl> Date: Thu, 19 Feb 2004 12:26:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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:29:42 -0000 > Greetings, > I am running 5.1-release. I created the file > /var/cron/tabs/root . It is owner root, group wheel. > permissions are -rw------- > > I have the following entry in the file root > > 0 22 2-31 * * /usr/local/bin/rsync -av /dept2/Marketing/ /data/Marketing > 2>&1 /r > oot/rsync.log > > Of course the line above is all on one line. > > Well, this command did not run last night. No /root/rsync.log file was > created. > No email was generated. Zip. > > what did I screw up to prevent cron from running the command ? You did it by hand instead of using the more automated method. Although you got the ownership/permissions correct, I bet you didn't restart the cron daemon (which is required so that it sees the newly created crontab.) You should really use "crontab -e" to edit/create crontab files. It will look after ownership/permissions automatically, as well as kicking the cron daemon. -- Matt Emmreton