Am 11.02.2010 14:41, schrieb Corinna Vinschen: > 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.
Hi everyone, let's not play Chinese Whispers. :-) I am the one who reported this issue to Pierre and who provided the logs. Windows 7 Professional 32-bit (German), build 7600, this computer is not a domain client, but standalone. Cygwin 1.7.1 release, cron logging to syslog-ng. Running cron as dedicated user fails for me - see the logs Pierre referred to. Configuring cyglsa as setuid method and running cron as "SYSTEM" works for me. Is trying the CVS or a snapshot (which one?) worthwhile? Anything besides cygwin1.dll to be replaced for a test? Best -- Matthias Andree -- 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