Re: [Toolserver-l] Job scheduling and mail receiving
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In article <4d516a08.5050...@surfeu.ch>, Dr. Trigon wrote: > Just a short question in [1] is mentioned how to trigger a mail in case > > * the job starts > * the job finishes > > what about > > * the job print something to stdout like for CRON jobs (in the early > days... ;)) I don't think there's a built-in method of doing this. You could use a wrapper script that did something like: #! /bin/ksh /path/to/mytool 2>&1 | mailx -s "Tool output" $LOGNAME Or, if you only wanted to receive output on failure: #! /bin/ksh f=$(mktemp) trap "rm -f $f" 0 /path/to/mytool >$f 2>&1 || <$f mailx -s "Tool output" $LOGNAME Or only if the command generated output: #! /bin/ksh f=$(mktemp) trap "rm -f $f" 0 /path/to/mytool >$f 2>&1 test -s $f && <$f mailx -s "Tool output" $LOGNAME ... etc. I think you're the first person who's asked about this, but it seems like a useful feature, so I'll see if there's a way to make it easier. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1R7FIACgkQIXd7fCuc5vKEPgCdEJj19ST9Kmz1jknYCtFSo09x iH0AnRMSq1OPN4N+20/8MtsaxmjgO8Ac =3lS2 -END PGP SIGNATURE- ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Job scheduling and mail receiving
The output of tools which write direct-to-stdout should be sent to you by e-mail to your toolserver e-mail. If you set an adress to relay the mailings to, then you'll get cron jobs output there. Works for me, though. Although, this ain't work from scratch for cronsubbed tools. On Tue, Feb 8, 2011 at 6:06 PM, Dr. Trigon wrote: > Hello all > > Just a short question in [1] is mentioned how to trigger a mail in case > > * the job starts > * the job finishes > > what about > > * the job print something to stdout like for CRON jobs (in the early > days... ;)) > > Thanks a lot for answering > Greetings > Dr. Trigon > > [1] > https://wiki.toolserver.org/view/Job_scheduling#Receiving_mail_when_the_job_starts_or_finishes > > ___ > Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) > https://lists.wikimedia.org/mailman/listinfo/toolserver-l > Posting guidelines for this list: > https://wiki.toolserver.org/view/Mailing_list_etiquette > -- З павагай, Павел Селіцкас/Paul Selitskas Wizardist @ Wikimedia projects p.selits...@gmail.com, +375257408304 Skype: p.selitskas ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
[Toolserver-l] Job scheduling and mail receiving
Hello all Just a short question in [1] is mentioned how to trigger a mail in case * the job starts * the job finishes what about * the job print something to stdout like for CRON jobs (in the early days... ;)) Thanks a lot for answering Greetings Dr. Trigon [1] https://wiki.toolserver.org/view/Job_scheduling#Receiving_mail_when_the_job_starts_or_finishes ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Maintenance for schema changes, now
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In article , Tim Landscheidt wrote: > one obvious solution would be to treat the Toolserver database servers > as part of WMF's domain so they can use their SOPs (*1) to maintain > them instead of manually coordinating with the Toolserver admins (or > not). I don't think that would be any easier. Our database systems are completely different from theirs, so it would require all WMF admins to learn (and remember) a new procedure before they could change anything on their side. Since they usually don't think to notify us of major changes in advance, I don't think they would be very happy with that. - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk1RU9EACgkQIXd7fCuc5vIpCwCgsJoicthjjp4n3xNQxZ6UdKdk BnAAn0EsQyZWlk11mIJxIZPFQAU/sH7u =T5Rg -END PGP SIGNATURE- ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Re: [Toolserver-l] Maintenance for schema changes, now
River Tarnell wrote: >> Given WMDE's recent fundraising changes which now allow sup- >> porting WMF directly, are there any plans to blur the clear >> distinction between WMF's farm and the Toolserver database >> servers with the accompanying headaches in the near future? > Not that I know of. What sort of changes were you expecting? I was expecting nothing :-). But as the Toolserver was miss- ing on WMF's radar in the past several times, one obvious solution would be to treat the Toolserver database servers as part of WMF's domain so they can use their SOPs (*1) to maintain them instead of manually coordinating with the Toolserver admins (or not). Tim (*1) With a twist for the user databases/access restric- tions, of course. ___ Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
