[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] MacOSX email
- Date: Thu, 4 Oct 2012 02:32:07 +0000
- From: "Jewell, Chris" <C.P.Jewell@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] MacOSX email
On 3 Oct 2012, at 17:14, Jewell, Chris wrote:
> I'm trying to get round the issue with /usr/bin/mail processes getting stuck on MacOSX. I read the "Troubleshooting" section of the manual, trying out the diagnostic:
> $ uname -a | mail -v my@xxxxxxxxxxxxxxxx
> which returned an error. So, I adjusted my Postfix configuration to explicitly include my organisation's SMTP mail relay, and now I can receive emails with the uname info just fine.
> However, the /usr/bin/mail processes are still getting stuck. There's nothing in the Condor logs, the mail.log, or system log that contains any information on why the processes are sticking. Does anyone have the crucial bit of information I'm missing?
As I followup, I tried creating a bash wrapper for /usr/bin/mail containing the command above:
uname -a | /usr/bin/mail -s "[Test for condor]" myemail@xxxxxxxxxxx
When I set MAIL=/path/to/my/script, I receive the expected "uname" email and no stray mail processes. I expect what is happening is that on OSX, mail is never receiving an EOF from Condor, and is therefore hanging around expecting more input to the message body. Is my assumption correct, I wonder?