On Fri, 20 Sep 2002, Simon Byrnand wrote: > >Or Qpopper flags are set to leave them behind. They're another way of > >seeing whan a user last popped. > > Would that prevent new sessions from logging on later though ?
No. > And if so, > what would be the point ? Later sessions will only be blocked in the face of user.pop files if the process ID referenced stille exists. > It sounds like in his case the stale .pop files are preventing him from > logging in again, so I doubt thats the case here. > > It needs to be established whether they're really stale, or whether the > popper process is just taking a long time to exit after a session is lost. Yes it does. Every time I've gone through this I've found there's a pop session left hanging > I found that it could take anywhere from 5 to 15 minutes for a session to > time out if the user "dissapeared" completely (eg modem hangup) You can tune this at startup. Check the -T flag.
