At 2:16 PM -0500 1/10/01, A. M. Salim wrote:
> First do a "ps" command
>
> ps awxu|grep pop3
>
> This will identify the pop3d process that is the locked users's.
>
> Then kill that process (kill -9 PID#) where PID# is the process ID number
> Do not do a "killall pop3d" ! Only kill that user's pop3d
>
> then you should check the file "/var/spool/mail/username" and if it is of
> non-zero size, then some emails came in since the lock happened. Execute
> these commands:
>
> cd /var/spool/mail
> cat username >> .username.pop
> mv .username.pop username
> rm username.lock
If you really are talking about pop3d and not Qpopper, ignore the
rest of this message.
If you are using Qpopper, don't kill the popper process. Usually
just leave it alone and it will clean up and go away. Only in
unusual circumstances is it necessary to do anything, and then a HUP
signal should be used. That lets it clean up the files itself, so
there is no need to do anything else. The .user.pop and user.lock
files go away without you doing anything else.
