Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 10 Jul 2001 14:20:22 +0200 From: Corinna Vinschen To: cygwin Subject: Re: Fwd: Re: CRON and time Message-ID: <20010710142022.R8578@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <5.1.0.14.2.20010710131544.03f40038@imap.local.mscha.com> <5.1.0.14.2.20010710131544.03f40038@imap.local.mscha.com> <20010710134102.Q8578@cygbert.vinschen.de> <5.1.0.14.2.20010710134941.026f4d78@imap.local.mscha.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20010710134941.026f4d78@imap.local.mscha.com>; from cygwin@mscha.com on Tue, Jul 10, 2001 at 01:52:10PM +0200 On Tue, Jul 10, 2001 at 01:52:10PM +0200, Michael Schaap wrote: > At 13:41 10-7-2001, you wrote: > >No, I don't think it's worth to add that to the cron README. It's > >a problem which always lurks for a chance to mess things up. > > What I meant is, this behaviour is very different from cron on UNIX, where > cron sets PATH by default to /usr/bin:/bin. > But I just checked, and guess what - you already mention it. :-) I do? .... aahh, you just meant the part about $PATH. Ok, that's a must. BTW, the same problem appears for sshd, rshd, login, etc. In all these cases the environment must be preserved when running under Cygwin. So, if anybody tries to port some daemon process, be aware of that environment propagation problem under Cygwin. Ok, now it's in the mailing list archive. When I mess up the next daemon that way, just send me the link to this mail. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/