From owner-freebsd-questions@FreeBSD.ORG Tue Aug 11 23:32:32 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 029351065673 for ; Tue, 11 Aug 2009 23:32:32 +0000 (UTC) (envelope-from vogelke@hcst.com) Received: from beta.hcst.com (beta.hcst.com [192.52.183.241]) by mx1.freebsd.org (Postfix) with ESMTP id B4D6E8FC16 for ; Tue, 11 Aug 2009 23:32:31 +0000 (UTC) Received: from beta.hcst.com (localhost [127.0.0.1]) by beta.hcst.com (8.13.8/8.13.8/Debian-3) with ESMTP id n7BNWUHn012835 for ; Tue, 11 Aug 2009 19:32:30 -0400 Received: (from vogelke@localhost) by beta.hcst.com (8.13.8/8.13.8/Submit) id n7BNWUTl012834; Tue, 11 Aug 2009 19:32:30 -0400 Received: by kev.msw.wpafb.af.mil (Postfix, from userid 32768) id 584B6B7B6; Tue, 11 Aug 2009 19:21:08 -0400 (EDT) To: freebsd-questions@freebsd.org In-reply-to: <4d4e09680908110750s68cb93c3r1cad8277012920d5@mail.gmail.com> (message from Identry on Tue, 11 Aug 2009 10:50:54 -0400) Organization: Oasis Systems Inc. X-Disclaimer: I don't speak for the USAF or Oasis. X-GPG-ID: 1024D/711752A0 2006-06-27 Karl Vogel X-GPG-Fingerprint: 56EB 6DBF 4224 C953 F417 CC99 4C7C 7D46 7117 52A0 Message-Id: <20090811232108.584B6B7B6@kev.msw.wpafb.af.mil> Date: Tue, 11 Aug 2009 19:21:08 -0400 (EDT) From: vogelke+unix@pobox.com (Karl Vogel) Subject: Re: location of user crontab files? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vogelke+unix@pobox.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 23:32:32 -0000 >> On Tue, 11 Aug 2009 10:50:54 -0400, >> Identry said: I> Where are user crontab files stored in the file system? I want to make I> sure this info is backed up. They're in /var/cron/tabs. If you're using individual crontab files, be sure to rename /etc/crontab or you might have duplicated cronjobs running simultaneously. I use the file header beneath my signature for crontab files, so I don't forget what field goes where. It's also handy to define an environment variable in case a program should behave differently when run under cron. -- Karl Vogel I don't speak for the USAF or my company # ==================================================================== # Everything on a line is separated by blanks or tabs. # Set CRON so scripts know when they're being run non-interactively. CRON=yes SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin # ==================================================================== #+--------------------------- Minute (0-59) #| +----------------------- Hour (0-23) #| | +----------------- Day (1-31) #| | | +------------- Month (1-12) #| | | | +--------- Day of week (0-6, 0=Sunday) #| | | | | +---- Command to be run #| | | | | | #v v v v v v # ==================================================================== # Jobs queued for later execution */5 * * * * /usr/libexec/atrun # -------------------------------------------------------------------- # Do daily/weekly/monthly maintenance 1 3 * * * periodic daily 10 22 * * * periodic evening 15 4 * * 6 periodic weekly 30 5 1 * * periodic monthly ..