Am Do, den 22.04.2004 schrieb Tim Alberts um 22:35: > I am curious if two programs (procmail and ipop3d or other) try to access the > same email file that is locked, what program is writing the error message > into the mail file? My understanding of two programs accessing the same file > at the same time is a bunch of garbage and bad things happen. Not a clean > consistently formated error message being written into the mail file. procmail and ipop3d running is not a problem. I am running that long enough, on Redhat and now on Fedora, and I never got any problem. As long as procmail is delivering new email to the $user mbox for new unread mail in /var/spool/mail the ipop3 or imapd gets no lock on the file. Again, I am sure you are doing something strange. See i.e. the following bugzilla entry - not a bug! -: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=120196 So we need more input what you are doing. Is there a way you can reproduce the case when the "error" occurs? You wrote with a clean new $user mbox file there is no problem. So it will be very good to know what you did just before the error in maillog occurs. You may to precisely describe your mail setup (including procmail filter script) and which actions you run. Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2179.nptl Sirendipity 22:47:31 up 4 days, 5:33, load average: 0.14, 0.17, 0.15 [ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ] my life is a planetarium - and you are the stars
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
