[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] wishlist for notification messages

One could add a global and local (per submit file) configuration option "FORMATTED EMAILS", and make the default "=no" the present format. "=yes" would be an easier to parse format.

No compatibility breakage unless explicitly desired.

Then, if desired, in a later development release (i.e. a new series where it is expected that things will break backwards compatibilty), the default can change to formatted emails instead.

Alternatively, the present format can be preserved, but one could append a formatted stanza which begins and ends with a consistent string (as x509 certificates do).

foo = bar
fred = wilma

On May 21, 2005, at 4:43 PM, Derek Wright wrote:

On Sat, 21 May 2005 10:18:04 -0400  Dan Christensen wrote:

I was wondering if there could be a few changes to the format/content
to make it easier for both people and machines to parse.

those are all nice suggestions, thanks. i'll see if we can work those into an upcoming development release. the only potential snag is if people already are parsing the emails, they'll scream about changing the format. all you pesky users make our job so much harder... ;)

1) Make the "Your condor job" line more easily parsable.  The format
   I suggest above makes it easier to find the "killed by ..." or
   "exited normally with exit code ..."  information, since it'll
   always be near the left column.  (Also, I intend to write a script
   which when fed such an e-mail message, resubmits the job).

instead of having a script parse emails to resubmit jobs that failed with a certain code/signal, you should probably check out the "on_exit_remove" setting in your submit description file:

(search for "on_exit_remove").

-derek (condor team)

_______________________________________________ Condor-users mailing list Condor-users@xxxxxxxxxxx https://lists.cs.wisc.edu/mailman/listinfo/condor-users