From owner-freebsd-questions Wed Apr 1 06:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06107 for freebsd-questions-outgoing; Wed, 1 Apr 1998 06:29:33 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06100 for ; Wed, 1 Apr 1998 06:29:29 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id JAA19303; Wed, 1 Apr 1998 09:28:24 -0500 (EST) Date: Wed, 1 Apr 1998 09:28:24 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: chas cc: FreeBSD Questions Subject: Re: Mailbox locked In-Reply-To: <3.0.32.19980401161908.009ef270@peace.com.my> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm coming into this rather late, but have you looked for any possible permutation of locking in /var/mail/$USER? Like a "." lock or "~" lock? If you get really desperate you can use lsof to see if any programs are holding the file open. Perhaps there's a zombie process grabbing it? Charles Sprickman spork@super-g.com ---- "I'm not a prophet or a stone-age man Just a mortal with potential of a superman I'm living on" -DB On Wed, 1 Apr 1998, chas wrote: > At 09:43 AM 4/1/98 +0800, Dean Hollister wrote: > >>>Hello, > >>> > >>>We have a user who's mailbox has been locked somehow. I need to clear the > >>>lock but cannot locate a lock file anywhere. Where would I expect to find > >>>it? > > >> A POP locked mailbox? Check for a file /var/mail/${USERNAME}.pop.lock (or > >> .${USERNAME}.pop.lock). > >> > >> The campus Solaris POP server has this problem constantly. They finally > >> created a script called 'unpop' that kills this file. > > > >Hmmmm.... Nothing like this is present... > > > >Elm, and Pine both report mailbox is read-only... > > Not sure I can help you since you mention Elm/Pine but > I've suffered similar locked mailboxes when the > user's mail client chokes and crashes whilst > downloading/decoding a very large attachment or > many messages. I attribute the subsequent "mailbox > locked" errors to the socket connection not being > closed in an orderly manner. > > In such circumstances, I've checked for lock files but > found none. Usual cure is to restart the POP server > and inetd but that rarely works... so I resort to the > usual cure-all : reboot. (obviously it would be nice > to not have to do this and disrupt all the other users > so I'm all ears for surefire ways of curing this : one > user in particular managed to lock his mail box very > frequently) > > chas > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message