From owner-freebsd-hackers Fri Jun 28 00:37:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA14880 for hackers-outgoing; Fri, 28 Jun 1996 00:37:38 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA14842 for ; Fri, 28 Jun 1996 00:36:03 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA21302; Thu, 27 Jun 1996 20:23:07 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA14454; Thu, 27 Jun 1996 20:21:41 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA02454; Thu, 27 Jun 1996 20:04:32 +0200 (MET DST) From: J Wunsch Message-Id: <199606271804.UAA02454@uriah.heep.sax.de> Subject: Re: no subject (file transmission) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 27 Jun 1996 20:04:32 +0200 (MET DST) Cc: pechter@shell.monmouth.com, freebsd-hackers@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <29794.835839033@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 26, 96 06:30:33 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > 2. Declare the BSD method (the REAL original crontab) the winner. > > I think this is probably our best bet. Objection. I voted against /etc/crontab back in the old days, and i'm still against it (and always kill it as soon as i've installed a system). There's only a few things where i'm stating SysV to have the better approach, but per-user crontabs certainly belong into this category. Remember, the original BSD crontab was even more braindead in that it didn't allow crontab entries for users other than root, and the current /etc/crontab would make a mess for crontab(1) to allow for per-user cron commands, while the existing approach with one file per user is there && has proven to work. On the opposite, i don't see anything /etc/crontab would gain us that /var/cron/tabs/ doesn't already give us as well. (Not counting nostalgic feelings. :) Despite of this, i consider a world-readable /etc/crontab a BIG security hole. Read "The Cuckoo's egg" for why intruders do like to know when exactly system maintenance jobs are about to run... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)