From owner-freebsd-questions@FreeBSD.ORG Thu Nov 3 21:56:54 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 67B9316A41F for ; Thu, 3 Nov 2005 21:56:54 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E2FA43D46 for ; Thu, 3 Nov 2005 21:56:53 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by aiolos.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA3Lup1e004622; Thu, 3 Nov 2005 23:56:52 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA3LuiqC034363; Thu, 3 Nov 2005 23:56:44 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA3Luiog034362; Thu, 3 Nov 2005 23:56:44 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 3 Nov 2005 23:56:44 +0200 From: Giorgos Keramidas To: Brandon Hinesley Message-ID: <20051103215644.GA34288@flame.pc> References: <20051103214610.GA34171@flame.pc> <001a01c5e0c0$c71d0e40$6800a8c0@BrandonH> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001a01c5e0c0$c71d0e40$6800a8c0@BrandonH> Cc: freebsd-questions@freebsd.org Subject: Re: Cron Job will not run. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 21:56:54 -0000 On 2005-11-03 13:51, Brandon Hinesley wrote: > Yes, it is. > -rwxr-x--- 1 root wheel 1827 Nov 3 12:43 bkup-daily > > >>I don't have to export /usr/local/Backup/scripts, right? > > >Hmmm, no, but is the script executable? That's odd. You'll have to schedule this script to run some time in the near future, and then stop cron. Run cron manually, as root, specifying at least the following debugging options and watch out when the scheduled event tries to run for interesting output on your terminal: # cron -x load,misc,pars,proc The meaning of these is explained in the manpage of cron, where all the rest of the debugging options are listed too. - Giorgos