From owner-freebsd-questions Fri Feb 15 13: 2:59 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx0.inoc.net (mx0.inoc.net [64.246.130.30]) by hub.freebsd.org (Postfix) with ESMTP id 56D9D37B400 for ; Fri, 15 Feb 2002 13:02:55 -0800 (PST) Received: from nimbus (unverified [10.0.0.111]) by mx0.inoc.net (Vircom SMTPRS 5.1.202) with ESMTP id ; Fri, 15 Feb 2002 16:02:53 -0500 Reply-To: From: "Robert Blayzor" To: , Subject: RE: Sendmail POP Lock Date: Fri, 15 Feb 2002 16:02:53 -0500 Organization: INOC, LLC Message-ID: <02f601c1b664$22980ee0$6f00000a@z0.inoc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <3.0.5.32.20020215140823.00e34990@mail.sage-american.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG More than likely if you see this poplock error, if you do a: "ps auxwww" You'll probably see a qpopper session open by the owner. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net Portable: Survives system reboot. > -----Original Message----- > From: jacks@sage-american.com [mailto:jacks@sage-american.com] > Sent: Friday, February 15, 2002 3:08 PM > To: rblayzor@inoc.net; freebsd-questions@freebsd.org > Subject: RE: Sendmail POP Lock > > > Thanks, Robert... yes, I looked back at this post before I posted my > question. But as I say in my later post, this is only a test > server and > there should not have been any other user session, although > it might have > thought so.... I figured this was another problem without an > answer yet.... > > > At 02:56 PM 2.15.2002 -0500, Robert Blayzor wrote: > >I'll post this back into the list as it was just a few days ago: > > > >If you are running Qpopper (POP3) this is a common problem. This > >happens when someone tries to pop into the same account when another > >session is already active. Or possibly the qpopper session crashed > >leaving the poplock file undeleted. > > > >There is no fix. You simply don't have multiple pop sessions. In > >practice, it's not a good idea to do so. > > > > > >-- > >Robert Blayzor, BOFH > >INOC, LLC > >rblayzor@inoc.net > > > >'Life is like a spoonful of Drain-O, it feels good on the > way down but > >leaves you feeling hollow inside' > > > > > > > >> -----Original Message----- > >> From: owner-freebsd-questions@FreeBSD.ORG > >> [mailto:owner-freebsd-questions@FreeBSD.ORG] On Behalf Of > >> jacks@sage-american.com > >> Sent: Friday, February 15, 2002 1:05 PM > >> To: freebsd-questions@freebsd.org > >> Subject: Sendmail POP Lock > >> > >> > >> I've just now set up a mail server using sendmail. Now, I see > >> that there is > >> a constant lock ".sageame.pop" on the main mail box > "sageame". Popper > >> installed and sendmail is configured. What did I forget to do > >> to cause this > >> freezeup....? > >> > >> Best regards, > >> Jack L. Stone, > >> Server Admin > >> > >> =================================================== > >> Sage-American > >> http://www.sage-american.com > >> jacks@sage-american.com > >> > >> "My center is giving way, my right is in retreat; > >> ....situation excellent! ....I shall attack!" > >> =================================================== > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-questions" in the body of the message > >> > > > > > > > > Best regards, > Jack L. Stone, > Server Admin > > =================================================== > Sage-American > http://www.sage-american.com > jacks@sage-american.com > > "My center is giving way, my right is in retreat; > ....situation excellent! ....I shall attack!" > =================================================== > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message