From owner-freebsd-questions Mon May 18 15:58:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00847 for freebsd-questions-outgoing; Mon, 18 May 1998 15:58:54 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00700 for ; Mon, 18 May 1998 15:58:23 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id PAA10246; Mon, 18 May 1998 15:28:33 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 18 May 1998 15:28:33 -0700 (PDT) From: Doug White Reply-To: Doug White To: Richard Coleman cc: questions@FreeBSD.ORG Subject: Re: root's crontab? In-Reply-To: <199805172001.QAA16435@cypress.math.gatech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 May 1998, Richard Coleman wrote: > When I do "crontab -l" as root, the system states that root has no > crontab. Yet it apppears the file /etc/crontab is functioning as > root's crontab (since logfiles are being rotated, etc.). This is > counter-intuitive. Is there a rationale for this behavior? Discourages people from logging in as root to change root's crontab, and (IMHO) it separates system tasks (like daily maintenance) from personal tasks (filtering root's mail). I noted that the Linux box next to me here (which I am NOT using!) does it this way. It threw me when /etc/crontab didn't exist. > Also, the fact that this file is world-readable, seems like a > bad idea (a small, but potential security risk). cron runs a root so you can make it 500 if you want. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message