From owner-freebsd-questions Thu May 4 17:51:24 2000 Delivered-To: freebsd-questions@freebsd.org Received: from gargoyle.apana.org.au (brisba6.lnk.telstra.net [139.130.66.200]) by hub.freebsd.org (Postfix) with ESMTP id 60C0B37B5A6 for ; Thu, 4 May 2000 17:51:17 -0700 (PDT) (envelope-from dougy@gargoyle.apana.org.au) Received: (from uucp@localhost) by gargoyle.apana.org.au (8.8.8/8.8.8) id KAA09949 for ; Fri, 5 May 2000 10:51:14 +1000 (EST) (envelope-from dougy@gargoyle.apana.org.au) Received: from roadrunner.apana.org.au(203.3.126.132), claiming to be "ROADRUNNER" via SMTP by gargoyle.apana.org.au, id smtpdka9946; Fri May 5 10:51:00 2000 Message-ID: <018e01bfb62c$58481b00$847e03cb@ROADRUNNER> From: "Doug Young" To: Subject: "bad day_of_the_month" (yes really !!!) cron questions Date: Fri, 5 May 2000 10:51:23 +1000 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 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to have remote systems email a copy of various logs at to me at sheduled times, & I understand that "cron" is supposed to be capable of doing this. What I don't understand is exactly how to go about it. I followed the instructions in Complete FreeBSD, and even though there's a file "/usr/bin/crontab", when I run "crontab -l" I get a message "no crontab for root" Now this sounds weird, because I understood from "man cron" & "man crontab" that a bunch of processes are controlled from the root cron, so what gives here ?? I then tried running "crontab crontab", but that just told me "crontab":0: bad day_of_month crontab: errors in crontab file, can't install Thats the first I knew there was such a thing as gender in computers !!!! .... now I know there is a theory that the male of the species is affected by chronological factors as well as the more commonly known female variety, but I really don't think thats the cause of this particular problem. For what its worth I did have a bad BIOS battery a while back that caused system time to go back to 1994, but its OK right now. How do I convince crontab that the system is running the correct time now, or what else needs to be done to sort this out ?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message