From owner-freebsd-questions Wed Nov 19 17:28:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22246 for questions-outgoing; Wed, 19 Nov 1997 17:28:36 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22238 for ; Wed, 19 Nov 1997 17:28:31 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id RAA03880; Wed, 19 Nov 1997 17:28:17 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 19 Nov 1997 17:28:17 -0800 (PST) From: Doug White Reply-To: Doug White To: Branson Matheson cc: nash@mcs.com, freebsd-questions@FreeBSD.ORG Subject: Re: Runnig FIND In-Reply-To: <19971119171746.42578@toth.hq.ferg.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Nov 1997, Branson Matheson wrote: > On Wed, Nov 19, 1997 at 04:02:46PM -0600, nash@mcs.net wrote: > > On 19 Nov, Branson Matheson wrote: > > > Everynight at the same time there is a cronjob that is probably > > > running it.. to find an idea of who/what/how/and why .. try reading > > > the manpage on crontab and running as root 'crontab -l' to see what > > > it is. > > > > /etc/daily & friends are executed out of /etc/crontab. Typing 'crontab > > -l' as root will produce 'crontab: no crontab for root'. > > Your right. I forgot about that little gem. That is a pain in the > tuckus. Could make for alot of headaches when searching for somthing > like this. Grrrr. Is there a reason for crontab -l *not* showing > /etc/crontab? Historical, probably. /etc/crontab is for systemwide maintenance processes, root's crontab would imply that those processes run for the root user's own business. I.e. atrun runs out of cron since it's a system thing, but a status monitor could run out of root's crontab. If you have root access though, why bother with the crontab(1) interface when you can just edit /etc/crontab directly? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major