X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: Subject: RE: Cron event logs says (*system*) NOT REGULAR... what does this mean Date: Thu, 8 Nov 2007 19:40:51 -0000 Message-ID: <001201c8223f$44c7adc0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 08 November 2007 19:29, Jerome Fong wrote: > I got cron working as a daemon, but now it stopped working again. I'm > getting the following errors in the cronevents output. Anyone know what > this means? Who owns the files mentioned? > 2007/11/08 11:02:18 [SYSTEM] /usr/sbin/cron: PID 1644: (*system*) NOT > REGULAR (/etc/cron.d/cron.daily) > 2007/11/08 11:02:18 [SYSTEM] /usr/sbin/cron: PID 1644: (*system*) NOT > REGULAR (/etc/cron.d/cron.hourly) > 2007/11/08 11:02:18 [SYSTEM] /usr/sbin/cron: PID 1644: (*system*) NOT > REGULAR (/etc/cron.d/cron.monthly) > 2007/11/08 11:02:18 [SYSTEM] /usr/sbin/cron: PID 1644: (*system*) NOT > REGULAR (/etc/cron.d/cron.weekly) This looks like the sort of confusion that cron can get into when it gets run as a mixture of system user and regular users... cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/