From owner-freebsd-questions Thu Feb 14 12:26:49 2002 Delivered-To: freebsd-questions@freebsd.org Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by hub.freebsd.org (Postfix) with ESMTP id CD7FA37B400 for ; Thu, 14 Feb 2002 12:26:41 -0800 (PST) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.6/8.11.6) with ESMTP id g1EKQUk28938; Fri, 15 Feb 2002 09:26:31 +1300 (NZDT) (envelope-from dan@lists.unixathome.org) Message-Id: <200202142026.g1EKQUk28938@lists.unixathome.org> From: "Dan Langille" Organization: DVL Software Limited To: Matt of the Long Red Hair Date: Thu, 14 Feb 2002 15:23:40 -0500 MIME-Version: 1.0 Subject: Re: crontab entries need a CR/LF at the end Reply-To: dan@langille.org Cc: Dan Langille , References: <20020214145934.Y46360-100000@bsd.smnolde.com> In-reply-to: X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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 14 Feb 2002 at 15:17, Matt of the Long Red Hair wrote: > I managed to reproduce this user's problem, but I had to work at it. > Simply editing the file with a text editor won't do it, since most leave a > \n at the end of even the last line. I had to do this: > > % echo -n "* * * * * ls ~/bin" > crontab > % crontab crontab FWIW, I was using joe > 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. Thank you. And agreed, definintely low-priority. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message