Index: [Article Count Order] [Thread]

Date:  Tue, 8 Apr 2008 09:54:40 -0500
From:  "Gerald Waugh" <gwaugh (at mark) frontstreetnetworks.com>
Subject:  [coba-e:12493] Re: Unable to lock - not running.
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <079f01c89988$7d1613e0$0101a8c0@systemax>
In-Reply-To:  <47FB45FA.8060709 (at mark) zbronx.com>
X-Mail-Count: 12493

Gustavo Silva [mailto:pseudo (at mark) zbronx.com] 
> 
> I started receiving the same message after doing the 
> flat-file password 
> db upgrade procedure. Or it was a BIG coincidence =)
> Anyway... Is this your case?
> 
 
> JMG-Support escreveu:
> > I am getting this email from the server.  Does anyone know 
> how to correct
> > this problem.  It started Sunday.
> >
> > From: Cron Daemon 
> > Subject: Cron <root@ns1> /usr/bin/php -q 
> /usr/local/mailwatch/mailq.php
> > MSG: Unable to lock - not running.
> >
Try 
  chmod 666 /var/run/mailq.lock
Might should be 644, but 666 seems to cure the problem
Not sure if it might get changed on a reboot...

Gerald