bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

procmail, fwrite and EFBIG


From: Noam Sturmwind
Subject: procmail, fwrite and EFBIG
Date: Tue, 10 Apr 2001 21:00:50 -0700 (PDT)

I've started receiving errors from procmail (MDA / mail filtering
program) when I download my email, and have traced the problem to some
strange fwrite behaviour. At first the errors were sporadic -- every few
messages, one would cause an error -- but now it happens on every message.

procmail reports in its log:
procmail: Bypassed locking "/var/spool/mail/noam.lock"
procmail: Assigning "LASTFOLDER=/var/spool/mail/noam"
procmail: Opening "/var/spool/mail/noam"
procmail: Acquiring kernel-lock
procmail: Error while writing to "/var/spool/mail/noam"
procmail: Truncated file to former size

And an strace on procmail shows:
write(5, "F", 1)                        = -1 EFBIG (File too large)
--- SIGXFSZ (File size limit exceeded) ---
fstat64(5, {st_mode=S_IFREG|0660, st_size=10240109, ...}) = 0
write(5, "rom address@hidden  Tue Apr"..., 7546) = -1 EFBIG (File too
large)
--- SIGXFSZ (File size limit exceeded) ---

Filehandle 5 is /var/spool/mail/noam:
open("/var/spool/mail/noam", O_WRONLY|O_APPEND|O_CREAT, 0667) = 5

Exactly what happens with fwrite seems to change every time I try
downloading; previously, a single fwrite call would be made to write the
message (a few kilobytes), but fwrite would return 1809 (same number for
every message). A second fwrite call would be made to write the remainder
of the message, and an EFBIG would then result. The current behaviour is a
bit different, as you can see.

The permissons on the mail spool are fine, and I have plenty of free disk
space on the partiation. For that matter, I can write to the file
manually (with a cat >> /var/spool/mail/noam for instance) with no
problem.

I'm unsure whether I made any system changes around the time that this
started; I know I had upgraded my kernel a few weeks before (2.2.x to
2.4.0; I'm now at 2.4.2). I may however have changed other system
files/libraries which I don't recall. I'm currently running glibc 2.2.2.

This problem has me totally baffled.. if anyone has encountered a similar
problem or has any pointers as to what to try next, I would be most
appreciative!

Noam Sturmwind






reply via email to

[Prev in Thread] Current Thread [Next in Thread]