Re: No root crontab in 4.6-RELEASE?
Thomas == Thomas Seck [EMAIL PROTECTED] writes: Thomas * Michael Sperber [Mr. Preprocessor] ([EMAIL PROTECTED]): Thomas == Thomas Seck [EMAIL PROTECTED] writes: Thomas [...] Cron also searches /etc/crontab Thomas Thomas The original poster obviously did not bother to read this document. Thomas Failing to read documentation and posting false claims on a public Thomas mailing list is a behaviour that drives me up the wall. That would be me, I guess. I never claimed there's no /etc/crontab file. I claimed there's no root crontab which, as some posters have noted, is something different. Thomas Uh, oh. My mind thought of the posting I originally replied to. Thomas What my hands made of it is what was finally sent out. Sorry. No problem! On the 4.3 systems I have around here, there's a root crontab starting like this: # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/adcrcln339/crontab installed on Mon Jun 11 20:53:28 2001) # (Cron version -- $FreeBSD: src/usr.sbin/cron/crontab/crontab.c,v 1.12.2.2 2000/12/11 01:03:31 obrien Exp $) It's no big deal. I was just wondering where that came from and why I'm no longer seeing it. Thomas I get your meaning. According to cvs, the behaviour of 'crontab -u root' Thomas was changed in version 1.12.2.3 of crontab.c, committed 2001/05/03 to Thomas RELENG_4. ... and here, finally, is the answer to my question. I never thought of looking at the history of crontab.c. Many thanks! -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: No root crontab in 4.6-RELEASE?
* Jason Andresen ([EMAIL PROTECTED]): [/etc/crontab vs. crontab -u root] ??? More visible? New people to the system can never find that file. Heck, I'm always forgetting where it is. It wouldn't be so bad if it just weren't so inconsistent. See cron(8), second paragraph. -- Thomas Seck This message was sent to a mailinglist I am subscribed to. Please send your replies to the list - and do *not* CC me. Thank you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: No root crontab in 4.6-RELEASE?
:* Jason Andresen ([EMAIL PROTECTED]): : :[/etc/crontab vs. crontab -u root] : : ??? More visible? New people to the system can never find that file. : Heck, I'm always forgetting where it is. It wouldn't be so bad if : it just weren't so inconsistent. : :See cron(8), second paragraph. : :-- :Thomas Seck : /etc/crontab should probably not be touched, nor should /etc/periodic, or upgrading the system will be nightmware. If you want to use the periodic mechanisms you can create your own periodic directory hierarchy ala /usr/local/etc/periodic, and if you just want to mess with your own root crontab you should use 'crontab -e' as root. If you want to override the system default /etc/periodic you can create your own /etc/periodic.conf (else the system uses the default /etc/defaults/periodic.conf). It's simple. See man periodic.conf. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: No root crontab in 4.6-RELEASE?
Date: Tue, 9 Jul 2002 09:51:03 -0700 (PDT) From: Matthew Dillon [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] :* Jason Andresen ([EMAIL PROTECTED]): : :[/etc/crontab vs. crontab -u root] : : ??? More visible? New people to the system can never find that file. : Heck, I'm always forgetting where it is. It wouldn't be so bad if : it just weren't so inconsistent. : :See cron(8), second paragraph. : :-- :Thomas Seck : /etc/crontab should probably not be touched, nor should /etc/periodic, or upgrading the system will be nightmware. If you want to use the periodic mechanisms you can create your own periodic directory hierarchy ala /usr/local/etc/periodic, and if you just want to mess with your own root crontab you should use 'crontab -e' as root. If you want to override the system default /etc/periodic you can create your own /etc/periodic.conf (else the system uses the default /etc/defaults/periodic.conf). It's simple. See man periodic.conf. Also, as far as I know, the use of local periodic(8) scripts via periodic.conf(5) entries in 999.local is supported. mergemaster(8) should catch changes in periodic.conf(5). R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message