From owner-freebsd-questions Thu Feb 14 13:36: 2 2002 Delivered-To: freebsd-questions@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 7185737B405 for ; Thu, 14 Feb 2002 13:35:56 -0800 (PST) Received: from [212.238.194.207] (helo=mailhost.raggedclown.net) by post.mail.nl.demon.net with esmtp (Exim 3.33 #1) id 16bTXn-00012E-00 for freebsd-questions@freebsd.org; Thu, 14 Feb 2002 21:35:55 +0000 Received: from angel.raggedclown.net (angel.raggedclown.intra [192.168.1.7]) by mailhost.raggedclown.net (Ragged Clown Mail Gateway [buffy]) with ESMTP id C71F213040 for ; Thu, 14 Feb 2002 22:35:54 +0100 (CET) Received: by angel.raggedclown.net (Ragged Clown Host [angel], from userid 1001) id A73A7225BC; Thu, 14 Feb 2002 22:35:54 +0100 (CET) Date: Thu, 14 Feb 2002 22:35:54 +0100 From: Cliff Sarginson To: freebsd-questions@freebsd.org Subject: Re: crontab entries need a CR/LF at the end Message-ID: <20020214213554.GA347@raggedclown.net> References: <44sn837pn4.fsf@lowellg.ne.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44sn837pn4.fsf@lowellg.ne.mediaone.net> User-Agent: Mutt/1.3.27i 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 On Thu, Feb 14, 2002 at 03:51:59PM -0500, Lowell Gilbert wrote: > 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. > Mmm, was about to point out something similar, it hangs on what the definition of a line is. I would say, Unix wise, it is a line, well let us say "row", of text ending in the newline character. I would hardly think this behaviour can be classed as a bug, or should be fixed for the very unusual case of someone not wanting their text editor to end a line in the usual way for them. (Mmm..unless you use it to write EDIfact messages by hand I guess...:) It is also an argument that cron may regard this is invalid due to a possibly corrupted crontab file - it reaches the end of file, expects a new line, there is not one, sounds like safe behaviour rather than a bug. -- Regards Cliff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message