[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nmh-workers] File descriptor leak in mhfixmsg?
From: |
Valdis Kletnieks |
Subject: |
[Nmh-workers] File descriptor leak in mhfixmsg? |
Date: |
Thu, 28 Jan 2016 18:37:29 -0500 |
After the recent discussion about mhfixmsg, I decided I was *totally*
fed up with the fact that grep kept missing things that were inside
base64 text/* blocks.
So trying to fix up a chunk of inbox died:
% mhfixmsg +inbox 1:9999 -verbose -decodetext 8bit
(....)
mhfixmsg: 3955, fix multipart boundary
mhfixmsg: /home/valdis/Mail/mhfixmsgWNiosi part 1, insert text/plain part
mhfixmsg: 3956, insert text/plain part
mhfixmsg: 3957, insert text/plain part
mhfixmsg: 3959, insert text/plain part
mhfixmsg: 3960, insert text/plain part
mhfixmsg: 3962, fix multipart boundary
mhfixmsg: /home/valdis/Mail/mhfixmsgPPSDsD part 1, will not decode because it
is binary (null character)
mhfixmsg: /home/valdis/Mail/mhfixmsgPPSDsD part 2, decode text/plain;
charset=US-ASCII
mhfixmsg: 3963, insert text/plain part
mhfixmsg: 3964, insert text/plain part
mhfixmsg: unable to open for writing /home/valdis/Mail/mhfixmsg6zYphW: Too many
open files
mhfixmsg: unable to replace broken boundary
mhfixmsg: unable to create temporary file in /home/valdis/Mail
mhfixmsg: unable to create temporary file in /home/valdis/Mail
pgpGmDkxJfqtY.pgp
Description: PGP signature
- [Nmh-workers] File descriptor leak in mhfixmsg?,
Valdis Kletnieks <=