-----Original Message-----
From: mindfuq(_at_)verizon(_dot_)net
Sent: Sunday, October 02, 2005 2:25 PM
[...]
procmail: Assigning "LASTFOLDER=mailing_lists/mythtv-users_2005"
procmail: Opening "mailing_lists/mythtv-users_2005"
procmail: Acquiring kernel-lock
procmail: Error while writing to "mailing_lists/mythtv-users_2005"
procmail: Truncated file to former size
procmail: Unlocking "mailing_lists/mythtv-users_2005.lock"
My scripts work fine otherwise. I don't see anything special about
this mailbox file:
# ls -l mythtv-users_2005
-rw------- 148017102 Oct 2 14:06 mythtv-users_2005
(We've got a user here with a 160Mb inbox, and he experiences
no problems with procmail delivery. Linux/FC4, fyi.)
You might want to check if you've exceeded some locally enforced
file quota.
My reading of the diagnostic above is not necessarily that the
file size was too large, but only that an error occurred while
writing to the mbox file, and the size was put back to the value
before the write was attempted. Maybe an NFS/samba file system
that dropped out due to network or availability problem? If you
have access to the system logs, that'd be worth a check.
Man procmail says the following:
Error while writing to "x"
Nonexistent subdirectory, no write
permission,
pipe died or disk full.
(You might want to double check the ownership on that file. Interesting,
that 'ls -l' didn't display the userid/groupid in example from your mail
message.)
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail