Am 17.02.2014 um 16:39 schrieb Prentice Bisbal:
> On 02/03/2014 07:05 AM, Reuti wrote:
>> Hi,
>>
>> Am 03.02.2014 um 09:02 schrieb Tim Landscheidt:
>>
>>> when a job fails, mails to root are sent with the subject
>>> "GE 6.2u5: Job 123 failed" (6.2u5-4/Ubuntu Precise). The
>>> body is marked as:
>>>
>>> | Content-Type: application/octet-stream
>>> | Content-Transfer-Encoding: base64
>>>
>>> This means (at least in Gnus) that I have to type K i to see
>>> the actual error report.
>>>
>>> Is there an option to mark the reports as text/plain like
>>> they appear to be?
>> This is done by your MTA (AFAICS not all are doing it), as it detects a
>> "0-backkspace-INFINITY" and encodes the "backspace". What can be done:
>> remove the 0-backspace in a wrapper and set "mailer" in SGE's configuration
>> to this:
>>
>> #!/bin/bash
>> sed "s/0"$'\b'"INFINITY/INFINITY/g" | mail -s "$2" "$3"
>>
> Reuti,
>
> I only have this problem for e-mails about jobs failing, not when they start
> or finish. If SGE is handling only adding the "0-backspace-INFINITY" to some
> of the e-mails it generates, shouldn't that be considered a bug?
Sure, it's tricky programming as first a macro is used:
#define FORMAT_LIMIT(x) (x==RLIMIT_INFINITY)?0:x,
(x==RLIMIT_INFINITY)?"\bINFINITY":""
and then always "number" + "string" is feed to something like:
sprintf("...%lu%s...%lu%s...",
FORMAT_LIMIT(soft-something),FORMAT_LIMIT(hard-something))
[on Linux, for other OSes different format placeholders are used]. It would
mean to split one print statement into four to handle hard or soft limit being
either a string or number each.
-- Reuti
> Thanks for the workaround. I'll try it on my system.
>
> Prentice
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
