At 12:18 PM -0500 2/21/02, Chris Sherman wrote:

>Hello,
>
>I've just recently installed Qpopper 4.03 which has solved a few 
>problems but now most users receive the following error message 
>serval times per day:
>-ERR [SYS/TEMP] maillock error 'Max tries exceeded' (4) on 
>'/var/spool/mail/username': File exists (17)
>
>Could anyone please help me out as to why I am receiving this 
>message and how to possibly get rid of it?

Probably the spool is locked by another process that is holding it 
locked for a relatively long time (maybe large files are being 
delivered).  One thing that could be done would be to replace the 
call on sleep(3) with doze(), which is an internal function that 
calls either sleep(3) or usleep(3) if it is available.  That would 
permit the maximum retries to be upped from 4 to something much 
larger, perhaps 10 or 50, and the delay between tries to be made much 
shorter and more random.  In other words, the same thing that is now 
done for the bulletin database.

If you want to try this out, edit common/maillock.c and change the 
call on sleep(3) to usleep(3), and change the call on Qmaillock() in 
popper/pop_dropcopy.c to pass '50' instead of '2', and in 
popper/pop_updt.c to pass '100' instead of '4'.

If this solves the problem for you, please let me know.

Reply via email to