At 8:14 AM -1000 6/11/01, Clifton Royston wrote: > > If so, this is a bug. The .user.pop file is also used as a >> mutual-exclusion lock to prevent more than one POP session at the >> same time. > > How does that work together with keeping it permanently around as a > zero-length file? Qpopper locks it with flock() or fcntl(). The presence of the file doesn't mean a session is active, because it's possible for a Qpopper process to die (especially 2.x) or be killed, which would leave the .user.pop file behind in any case.
- Changes in how keep-temp-drop works Clifton Royston
- Re: Changes in how keep-temp-drop works Butch Kemper
- Re: Changes in how keep-temp-drop works Jeff Earickson
- Re: Changes in how keep-temp-drop works Randall Gellens
- Re: Changes in how keep-temp-drop works Clifton Royston
- Re: Changes in how keep-temp-drop works Randall Gellens
- Re: Changes in how keep-temp-drop works Clifton Royston
- Re: Changes in how keep-temp-drop works Randall Gellens
- Re: Changes in how keep-temp-drop works Clifton Royston
- Re: Changes in how keep-temp-drop works Clifton Royston
- Re: Changes in how keep-temp-drop works Randall Gellens
