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

RE: [hobbit] LSF tests on Shire



Feel free to ahead and make the changes on The Shire...it's really just a wiki (dokuwiki to be exact).  If this is something you've found helpful, feel free to create a tutorial on the tutorials page as well.

=G=

From: Everett, Vernon [mailto:Vernon.Everett (at) woodside.com.au]
Sent: Thursday, September 11, 2008 2:52 AM
To: hobbit (at) hswn.dk
Subject: RE: [hobbit] LSF tests on Shire

We did, it bounced. :-(

________________________________
From: Lars Ebeling [mailto:lars.ebeling (at) leopg9.no-ip.org]
Sent: Thursday, 11 September 2008 2:48 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] LSF tests on Shire
Try this:

gn1 (at) sanger.ac.uk<mailto:gn1 (at) sanger.ac.uk>

--
Regards
Lars Ebeling

http://leopg9.no-ip.org
Hobbithobbyist

"It is better to keep your mouth shut and appear stupid than to open it and remove all doubt."
-- Mark Twain



----- Original Message -----
From: Everett, Vernon<mailto:Vernon.Everett (at) woodside.com.au>
To: hobbit (at) hswn.dk<mailto:hobbit (at) hswn.dk>
Sent: Thursday, September 11, 2008 7:17 AM
Subject: [hobbit] LSF tests on Shire

Hi

Does anybody know the current email address of Gildas Le Nadan, author of the lsf_mon.pl and lsf_queues.pl on the Shire?
My colleague managed to make a few improvements to these excellent scripts, and it might be good to fold the changes back into the code.

One of the changes he made, was if you run a test (from command line perhaps) and the $BB* variables are not defined, and you are on a terminal, then run and display output to standard-out.
He does this for most of the things he writes that are to be included into hobbit, and I believe it is a good idea, and should be adopted for all Hobbit script writers.

It's a little more difficult if the script is reliant on $BBHOME to access files, but if there is a way to run from command line, it should.

Regards
     Vernon




NOTICE: This email and any attachments are confidential.

They may contain legally privileged information or

copyright material. You must not read, copy, use or

disclose them without authorisation. If you are not an

intended recipient, please contact us at once by return

email and then delete both messages and all attachments.