X-Spam-Check-By: sourceware.org Message-ID: <445CACA3.9010001@well-dunn.com> Date: Sat, 06 May 2006 09:03:15 -0500 From: Mike Dunn User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Win2003 server and cron/sshd as services (1.5.19) References: <4457E24C DOT 2020303 AT well-dunn DOT com> <8e32b7255e82c71fc919a18ea47fb41e AT well-dunn DOT com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Indeed I did run it. Cron_diagnose complained about permissions that I fixed by chowning the files/directories to the Administrators group. But those changes did not change cron's behaivor. I did just test by running cron from the command line (not as a service), and it appears to work fine. I suspect, that it can only exec commands under my uid, since my account does not have things like SeCreateTokenPrivilege, etc. I would like to "su" to my cron_server (or sshd_server) uid to test out running the daemons without cygrunsrv, but I don't know how to switch users in cygwin with out ssh'ing to localhost. Login does not seem to work (giving me the message about the changes in ntsec) even after I added these rights to my user account: SeServiceLogonRight SeIncreaseQuotaPrivilege SeCreateTokenPrivilege SeAssignPrimaryTokenPrivilege One last thing. I fired up apache under my userid, and it sucessfully bound to port 80, (in my mind at least) debunking the fire wall theory. Any debugging tips would be greatly appreciated. Thanks Mike René Berber wrote: > Mike Dunn wrote: > > >> Good question ;). I have not been able to find one, but I don't >> necessarily know where to look (i'm not much of a windows guy). >> I'll keep looking, but cron is showing the same behaivor as sshd, and cron >> AFAIK does not bind to a tcp port. I had ruled out a firewall due to >> cron's behaivor. >> > > Valid point, have you tried cron_diagnose.sh? > -- 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/