Date:  Thu, 10 Apr 2008 21:48:53 -0500
From:  "JMG-Support" <JMG-Support (at mark) JMG-Enterprises.com>
Subject:  [coba-e:12542] Re: Unable to lock - not running.
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <001101c89b7e$94704770$bd50d650$@com>
In-Reply-To:  <10A795DFCACB4D3D9DB0965C4CE8BC29 (at mark) JMGEnterprises.local>
References:  <079f01c89988$7d1613e0$0101a8c0 (at mark) systemax> <10A795DFCACB4D3D9DB0965C4CE8BC29 (at mark) JMGEnterprises.local>
X-Mail-Count: 12542

Same here...  after the chmod change and a reboot.

John 


> -----Original Message-----
> From: Gustavo Silva [mailto:pseudo (at mark) zbronx.com]
> Sent: Tuesday, April 08, 2008 7:46 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:12514] Re: Unable to lock - not running.
> 
> Thanks Gerald.
> Surprisingly.. a reboot fixed it...
> Microsoft Style.
> 
> Kinds regards,
> Gustavo
> 
> Gerald Waugh escreveu:
> > 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
> >
> >
> >
>