X-Spam-Check-By: sourceware.org Message-ID: <445D1839.2060608@cygwin.com> Date: Sat, 06 May 2006 17:42:17 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin@cygwin.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051223 Fedora/1.5-0.2.fc4.remi Thunderbird/1.5 Mnenhy/0.7.3.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Win2003 server and cron/sshd as services (1.5.19) References: <4457E24C.2020303@well-dunn.com> <8e32b7255e82c71fc919a18ea47fb41e@well-dunn.com> <445CACA3.9010001@well-dunn.com> In-Reply-To: <445CACA3.9010001@well-dunn.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/