On Fri, 12 Aug 2011, 00:48:35 BST, [email protected] wrote: > > Thanks for the suggestions. I'll have to look at it later, though I > > wonder if it's simplest just to strip the backspace sequences post hoc. > > > > I'm actually more interested in under what circumstances you get the > > shepherd trace in the admin mail. > > Typically, it is after a job running on a machine that was powered > off, and so died, reports back : > > failed before writing exit_status:shepherd exited with exit status 19: > before writing exit_status
Right. The problem is that the mail is incomplete. > I think this was an issue I/we raised some time ago but was never > really concluded. > > However that's another issue. > > Given that these mails can/do get generated, fixing the usage of a > non-printing charcacter being piped into a mail process's message > buffer, which allows that mail process to then consider the buffer > in need of a base64 encoding, as opposed to simply delivering simple > plain text ouput, which is what is wanted here, is surely worth doing > of itself and, furthermore, the proposed soultion (admittedly the > fourth iteration of the original proposal!) solves that issue. I said I'd look at it, and I filed a bug so it doesn't get lost, but in my case that part of the mail is never generated anyway, so it's moot. The non-printing characters should obviously be fixed. -- Sent from a mobile; excuse the result. _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
