From owner-freebsd-questions Thu Feb 14 12:52: 8 2002 Delivered-To: freebsd-questions@freebsd.org Received: from be-well.ilk.org (lowellg.ne.mediaone.net [24.147.188.158]) by hub.freebsd.org (Postfix) with ESMTP id AD71937B417 for ; Thu, 14 Feb 2002 12:52:06 -0800 (PST) Received: (from lowell@localhost) by be-well.ilk.org (8.11.6/8.11.4) id g1EKpxf45643; Thu, 14 Feb 2002 15:51:59 -0500 (EST) (envelope-from lowell@world.std.com) X-Authentication-Warning: be-well.ilk.org: lowell set sender to lowell@world.std.com using -f To: freebsd-questions@freebsd.org Subject: Re: crontab entries need a CR/LF at the end References: From: Lowell Gilbert Date: 14 Feb 2002 15:51:59 -0500 In-Reply-To: Message-ID: <44sn837pn4.fsf@lowellg.ne.mediaone.net> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Matt of the Long Red Hair writes: > I'm not sure if this is a bug or not, but his observations are at least valid. > It seems bug-like to me, though probably not a very high priority one. The manual says: The entire command portion of the line, up to a newline or % char- acter, will be executed by /bin/sh or by the shell specified in the SHELL variable of the cronfile. so it sounds to me like it's performing as documented. So while there may be good arguments for changing the behaviour, it's certainly not a bug. I wouldn't support changing it, by the way; the definition of a line as "one or more characters ending in a newline character" is typical in Unix, and changing that for crontab would probably create more problems than it solves. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message