David, The problem turned out to be restricted perms on /tmp. Instead of finding them at 1777, I found them to be set to 755. How they got like that, I'm not sure. However, we were testing some new backup/restore software on the morning when the mail logs say the problem first started happening, and I had the backup admin perform some test "restores to alternate directories", to the /tmp directory on that server. That was Tuesday. I'm wondering if the restore process somehow changed the perms on the directory, and am following through with him on that hypothesis.
Ken -----Original Message----- From: David F. Skoll [mailto:[EMAIL PROTECTED] Sent: Thursday, February 03, 2005 4:52 PM To: '[email protected]' Subject: Re: [Mimedefang] "Cant open tmpfile" error On Thu, 3 Feb 2005, Cormack, Ken wrote: > Feb 3 16:16:09 mail02 mimedefang-multiplexor[574]: Slave 3 stderr: > MIME::Parser: can't open tmpfile: Invalid argument This is coming from deep in the guts of IO::File->new_tmpfile. Could you have a TMPDIR environment variable set that's pointing somewhere strange? Could /tmp be full? Regards, David. _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
