X-Spam-Check-By: sourceware.org Message-ID: <4461F92A.2020303@well-dunn.com> Date: Wed, 10 May 2006 09:31:06 -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> <445CACA3 DOT 9010001 AT well-dunn DOT com> <445D1839 DOT 2060608 AT cygwin DOT com> In-Reply-To: <445D1839.2060608@cygwin.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 Was there anything in particular you are referring to in the README, or is this a general RTFM comment? I have read the READMEs, googled the list for 5 days, picked apart the install scripts, tested with alternative services, reinstalled, etc. I would like to think that I've done my home work. I believe that I understand the permissions issue that you refer to. Clearly I ran cron under my UID as a diagnostic procedure; I have since reinstalled it a number of times (correcting the permissions indicated in the README) and cron_diagnose is happy. Can you suggest what may be wrong with permission beyond that? Thanks Mike Larry Hall (Cygwin) wrote: > On 05/06/2006, Mike Dunn wrote: >> 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. > > > Right. And by running it from the command line under your uid, you've > created > files under /var with permissions that will keep 'cron' from running as a > service using the sshd_server (which already has the ability to switch > user > contexts on W2K3). Your best bet here is probably to uninstall cron and > reinstall it, using the installation instructions in > /usr/share/doc/Cygwin/cron.README. > > -- 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/