From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27270 invoked by alias); 7 May 2004 02:00:00 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 27049 invoked from network); 7 May 2004 01:59:58 -0000 Received: from unknown (HELO dessent.net) (66.227.14.169) by sources.redhat.com with SMTP; 7 May 2004 01:59:58 -0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.30) id 1BLujE-0005Mg-GR for cygwin@cygwin.com; Fri, 07 May 2004 02:04:45 +0000 Message-ID: <409AED9A.A91CA4A0@dessent.net> Date: Fri, 07 May 2004 02:06:00 -0000 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: CRON problems References: <1083885162.409ac66a5ab06@topcat.ims.uaf.edu> <1083888621.409ad3eded2a0@topcat.ims.uaf.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com X-SW-Source: 2004-05/txt/msg00261.txt.bz2 Hank Statscewich wrote: > Great suggestion. In /var/log/cron.log there were 17 lines of: > /usr/sbin/cron: can't open or create /var/run/cron.pid: Permission denied > > So I just changed permission of the file to 777 and cron started up just fine. > I rebooted and lo and behold cron is still running. I'm changing permission > back to something more appropriate now. I am now a fully satisfied cygwin user. > Thansk for such a great port of linux onto windows, Cygwin is the best of both > worlds (at least for now :) Hmm, seems to me like checking ownership and permissions of cron.pid would be something the cron_diagnose.sh should do. What happened was that you ran it initially as your normal user account, and the pid file was created. Then when you tried to start it as a service, it was running as the SYSTEM account which didn't have permissions to overwrite the file. The solution would be to either just remove it and let cron recreate it, or "chown SYSTEM:SYSTEM /var/run/cron.pid". Then you could give it more restrictive permissions than 777, perhaps 640 or 600. Brian -- 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/