-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 01/13/2011 02:21 PM, Alex Brollo wrote:

2011/1/13 chris <chris@bjelleklang.org mailto:chris@bjelleklang.org>

It's possible to have multiple screens up at one time. Are you
terminating the screen before logout, or just disconnecting?

ctrl-a-d dissconnects, ctrl-a-\ terminates screen.

If you just disconnect from it, the screen will live on and be available
for you at the next login.

Thanks Chris, nevertheless I remember you... I' need an idiot-proof help.(Perhaps you are wondering: is toolserver a good place for an idiot? Yes, I just am asking the same question to myself...:-( )

The problem is: how can access into live screens, since they aren't named, to press that ctrl-a ? There's some help to enter into them, but it is written into a "basic linuxian" ... and man page of screen, as you ca imagine, doesn't help me.

Alex

To reattach to one of several running screens, use

screen -r 21068.pts-24.willow

The part after 'screen -r' is the first column of 'screen -list' If you've only got one screen running you can use 'screen x' to resume it.

regards Chris

It should be (rather) simple once you got how 'crontab'/'cronjob's work.

Then it' simple a fact of using it - preferrably - through 'cronie' and toghether with 'cronsub' to start the batch job...

Best is you install your crontab on 'submit.toolserver.org' as I understood from River's last mail "[Toolserver-l] New job submission servers".

Look also at [1] and [2].

By the way THANKS A LOT to TS TEAM for this (surprisingly) simple migration and new solution!!

Greetings Dr.Trigon

[1] https://wiki.toolserver.org/view/Crontab [2] https://wiki.toolserver.org/view/SGE#Converting_an_existing_cron_job_to_use_...

Am 13.01.2011 18:03, schrieb Alex Brollo:

Ok, I got it. Simply a matter of using Ctrl-D again and again. As stated into the help page on screens: "With the last screen closed you will log out.", No screens and no login pending.

Now, let's begin again from scratch, using batch job scheduling only...

Thanks!

Alex

---

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

This is my trouble. I read and read again Batch job page, but I couldn't find the right syntax for the simpler case: simply, how to run a /single/ script using batch job! Examples deal mainly with cron jobs: but how can I run a /single/ script like, even in into an interactive way to test it, ie:

The cronjob just triggers your batch job, so you can use the same commands in shell as in cron. But the command

/python example.py/

has now to be runned this way:

cronsub example.py

'cronsub' is just the "better" version to start a job than 'qsub' especially for python scripts. You have also to make the .py file executable which means use 'chmod 744' on it and add '#!/usr/bin/env python' as first line to your example.py file. May be you want to confer the mails on this list between Jan. 8. and Jan. 9. about this topic.

Next question. I'd like to run again my irc.py python script, designed to run into a screen forever. I can't understand why I'd wrap it into a crontable: it has simply to run once. When it was running, I run it into a screen simply with:

I don't know if you have to - the same procedure as you used should still work and also be ok... But when reading first [1] (even if its obsolete now) and then [2] you can see there is THE ADVANTAGE of having your script automatically re-started once the server re-starts (else your script is down until you start it again by hands). The other advantage is you won't have to use 'screen' in fact since this is to keep your script running by the moment you log out - but since the server runs your script this is not needed anymore. (I also used to use 'screen' to have my bot running all the time, most of it in 'sleeping' state, but it is much more convenient to re-write it in a way you can run it by cron, at a given interval, e.g. all 10 minutes... EXCEPT YOU HAVE to have a continous running one, e.g. to log the whole irc messages or else... ;)

May be someone else has some additional tips... But the toolserver wiki is a good place to start...

[1] https://wiki.toolserver.org/view/Phoenix [2] https://wiki.toolserver.org/view/Job_scheduling#Converting_a_Phoenix_tool_to...

Am 14.01.2011 10:05, schrieb Alex Brollo:

2011/1/14 Dr. Trigon <dr.trigon@surfeu.ch mailto:dr.trigon@surfeu.ch>

It should be (rather) simple once you got how 'crontab'/'cronjob's work.

This is my trouble. I read and read again Batch job page, but I couldn't find the right syntax for the simpler case: simply, how to run a /single/ script using batch job! Examples deal mainly with cron jobs: but how can I run a /single/ script like, even in into an interactive way to test it, ie:

/python example.py/

Next question. I'd like to run again my irc.py python script, designed to run into a screen forever. I can't understand why I'd wrap it into a crontable: it has simply to run once. When it was running, I run it into a screen simply with:

/python irc.py/

It simply listens at it.source #irc Recent changes channel, and writes selected & parsed data into a public txt file (so I can see from web if it's live or dead without logging into the server, and there's too a queue ready for another cron script, who uses that txt file)

How should I run it into a screen, with new settings? Remember... I'd like an idiot-proof suggestion. :-(

Alex

---

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

2011/1/14 Dr. Trigon dr.trigon@surfeu.ch

...

....

has now to be runned this way:

cronsub example.py

I got terribly frustrated.... till I tried:

cronsub hello $HOME/hello.py (and, better, cronsub -s hello $HOME/hello.py runs too).

Ok, "Hello world" of job scheduling runs. :-(

Alex