X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 11 Feb 2010 14:41:16 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cron & Windows 7 Message-ID: <20100211134116.GM28659@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <010601caaaca$58aa1e20$7b00a8c0 AT wirelessworld DOT airvananet DOT com> <4B73894B DOT 4060306 AT tpg DOT com DOT au> <014d01caab1d$bed91720$7b00a8c0 AT wirelessworld DOT airvananet DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <014d01caab1d$bed91720$7b00a8c0@wirelessworld.airvananet.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Feb 11 08:25, Pierre A. Humblet wrote: > ----- Original Message ----- > From: "Shaddy Baddah" > To: "Pierre A. Humblet" > Cc: cygwin > Sent: Wednesday, February 10, 2010 23:36 > > > | Hi, > | > | On 11/02/2010 3:28 AM, Pierre A. Humblet wrote: > | > I got reports that cron is having problems with Cygwin 1.7.1 on > | > Windows 7 - 32 bits. > | > They occur only with seteuid method 1, not with method 2 nor method 3. > | > | Based purely on the above (and not the rest of the report... sorry) I > | suspect it might be due to a problem that has just been fixed in CVS > | (http://cygwin.com/ml/cygwin-developers/2010-02/msg00037.html). If you > | have time to kill before someone of authority intervenes, you may want > | to try a snapshot (http://cygwin.com/snapshots/) and see if it helps. > | > > Thanks Shaddy, I will point this to the user. > However according to the mails on the developers' list I don't see why the > changes would apply to Method 1. > > Pierre No, that's not related. But we had a few reports on the list already concerning sshd and it seemed to be a problem with using a non-Domain cyg_server user running sshd, which lead to a crippled token: http://cygwin.com/ml/cygwin/2010-01/msg00334.html This is not related to W7, but should be a problem starting with Windows Server 2003. Pierre, you know a lot about this authentication stuff in Cygwin, you applied a couple of patches yourself, and you have a copyright assignment in place. If you think there's another problem lurking, please help with debugging and patches. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple