X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48C6F81C.7020000@cygwin.com> Date: Tue, 09 Sep 2008 18:26:36 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin@cygwin.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20070505 Remi/2.0.0.0-3.fc4.remi Lightning/0.8 Thunderbird/2.0.0.0 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: cron without sendmail generates bogus logfile names References: <84dde90809091503od758f6s6181346bb1c6f9f0@mail.gmail.com> In-Reply-To: <84dde90809091503od758f6s6181346bb1c6f9f0@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Linus Hicks wrote: > The "poor man's mailer" included as part of the cron package uses the > following construct to generate part of the filename used in making > log file names: > > DATE=$(date '+%Y%m%d_%H%M%S') > > It then generates the filename as: > > FILE="/tmp/cron.$DATE.$$.log" > > However, it seems to be tacking on a CR character at the end of the > DATE portion which messes up the generated filenames. I cannot > reproduce this behavior in sh running in an xterm window: Try running the mailer script through 'd2u'. If that doesn't work, it suggests a difference in the environment for the cron service versus your interactive shell. Any chance you have another, Win32- native "date" hanging around? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/