From owner-freebsd-current Tue May 2 19:02:55 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA23589 for current-outgoing; Tue, 2 May 1995 19:02:55 -0700 Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA23582 for ; Tue, 2 May 1995 19:02:43 -0700 Received: from metal.ops.neosoft.com (root@glenn-slip54.nmt.edu [129.138.5.154]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id VAA05333; Tue, 2 May 1995 21:02:35 -0500 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id UAA00325; Tue, 2 May 1995 20:02:31 -0600 From: Scott Mace Message-Id: <199505030202.UAA00325@metal.ops.neosoft.com> Subject: Re: bug: /usr/src/etc/crontab To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 2 May 1995 20:02:31 -0600 (MDT) Cc: current@FreeBSD.org In-Reply-To: <199505030022.RAA03443@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 2, 95 05:22:27 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 839 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > Does crontab really support the "who" column in /usr/src/etc/crontab? > > > > I thought that functionality was removed with the release of cron > > that we have? > > No, that functionality was added when we went with Vixie Cron 3.0. > ok, then why does this happen: /etc/crontab entry: 0 * * * * root /bin/ls when it runs I get: Subject: Cron root /bin/ls X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: Status: OR root: not found Subject: Cron /bin/ls X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: Status: OR .cshrc .hushlogin .login