On Fri, Sep 07, 2001 at 08:44:02AM -0700, Darren Dunham wrote:
> > Qpopper is unable to lock the maildrop during the QUIT. Possibly a
> > lot of mail is being delivered.
>
> Maybe. I'm more worried that to me the message is saying that it can't
> lock it because the file is no longer present.
>
> It all my testing (when I can't reproduce the problem) the .dbuser.pop
> file remains until the end of the session. In this case, it looks like
> the file is gone.
>
> The user can't log in, so I know they're not responsible for it. It
> doesn't happen often enough for me to be able to truss all the qpopper
> processes into log files and parse them.
>
> I was just wondering if anyone had seen something like this before. For
> now, I'm planning on turning off server mode and seeing if the problem
> goes away.
Belated followup: I haven't seen anything like this, in my experience.
Maybe you could use a tool like lsof to look for anything else which
might be processing files in the directory where your poptemp files
are?
One more possiblity - maybe the locking mechanism qpopper is using
isn't working, allowing two pop sessions to start concurrently for the
same user? See if you can tell what lock mechanism it's using, and
whether it's one that makes sense for your OS/architecture.
-- Clifton
--
Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
