Re: [cobalt-users] Raq2 .lock problem after RaQ2-en-Update-OS-3.0.pkg possible bug

["John Burgess" <john.burgess@xxxxxxxxxx>]

Yes, there is a better way.  I build a new IMAP and new POP servers from the
UofW source.  It is working to perfection I haven't had any pop problems
since.  If you want them, let me know,  I'll send you the source and
binaries if you want.  In the mean time, to recover from the lockfile
problem, without a reboot, edit the /etc/inetd.conf file, comment out the
pop server, save and do a kill -HUP on inetd.  Remove the lock files.  edit
/etc/inetd.conf and uncomment the pop server.  Save and do a kill -HUP again
on inetd.

John Burgess
fastex.net

----- Original Message -----
From: "Gerald Waugh" <gerald@xxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Friday, August 25, 2000 5:01 PM
Subject: RE: [cobalt-users] Raq2 .lock problem after
RaQ2-en-Update-OS-3.0.pkg possible bug


> Ok, guys,
> Another RaQ2 acting up I guess.
> You know, I can't keep spending most of my time keeping these cobalt
servers
> running. I really do have other things to do! I'll tell you what we have
NT
> servers at another location, and although we have to reboot them once in a
> while, we don't spend our days and nights keeping them operating!
>
> [root admin]# tail /var/log/maillog
> Aug 25 17:44:53 fsn1 in.qpopper[14704]: gw2003 at
www.frontstreetnetworks.org
> (216
> .175.178.40): -ERR [SYS/TEMP] maillock error 4: '/var/spool/mail/gw2003'
>
> This is my software
> Cobalt OS Release 4.0
> OpenSSH Server Release 2.1.1p2
> RaQ2-All-Security Release 3.0.1-6682
> RaQ2-All-System Release 2.98-6168
> RaQ2-Qpopper-Expr Release 2
> RaQ2-en-Update-OS Release 3.0
>
> I searched for this issue on the list and all I found was reboot, and
remove the
> locked files.
> There has to be a better way!
> Thanks!
>
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users