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

["Dan" <dan@xxxxxxxxxxxxx>]

> 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 et al:

Well, today, without warning, a technician from Cobalt went into my server
and installed OS Update 3.0. Of course, while he was doing this my POP
stopped working. It was only when I rebooted the server in an attempt to
clear what I thought was a problem that I got a call from Cobalt as if I had
done something wrong.
The server was working well. POP before SMTP was working, although it was OS
2.0.
After his install of OS 3.0, (and he immediately installed Qpopper 2.53), I
was unable to get POP before SMTP reinstalled. Any attempt to install it
broke POP completely.

So,  now <sarcasm>I'm lucky enough</sarcasm> to have OS 3.0 and all the
great patches that it brings me, but I no longer have POP before SMTP.
Normally this wouldn't be a big deal, but one reseller customer that covers
about 25% of my monthly colo costs is probably going to leave as many of her
clients use AOL and have no SMTP access.

Color (colour) me unhappy.

John, if you'd be interested in a little consulting, please email off-list
regarding your POP build that you've been successful with.

--
Dan Kriwitsky