delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Envelope-to: | cygwin AT cygwin DOT com |
Message-ID: | <002801c33994$a9770b00$30107a0a@morse.corp.wan> |
Reply-To: | "Michael Jervis" <mike AT skinmaster DOT co DOT uk> |
From: | "Michael Jervis" <mike AT skinmaster DOT co DOT uk> |
To: | <cygwin AT cygwin DOT com> |
Subject: | Mysterious Cron error solved |
Date: | Mon, 23 Jun 2003 15:35:12 +0100 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1106 |
I'd been trying to get cron running for a day or three. Came accross someone who had the EXACT same problem as me: http://www.cygwin.com/ml/cygwin/2003-03/msg00624.html But found no solution. Now I have solved it, so here is my solution: /var/run was set to be owned by my user. Not the SYSTEM user. Which meant that cron service was unable to write the cron.pid file into that folder. A swift chmod a+w allowed me to start cron. Hopefuly this will help someone else! Mike -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |