On 28.06.2013 09:32, Tibor Simko wrote:
Hi!
On Fri, 28 Jun 2013, [email protected] wrote:
Out of sheer curiosity: does putting bibsched to manual and run the task
really put to running status?
Yes, this is intended. When the queue is in manual mode, the admin can
decide which tasks to run manually in what order.
Understood that and even use it myself quite often.
However, in Ferrans case I wonder: why can he start a job /manually/,
that was scheduled, but did /not/ reach running status via the usual means?
Ie. what is the difference (there seems to be one) between run manually
and run automatically? It looks like that some inhibitor is gone when I
hit R that persists when the scheduler launches the same(?) command. As
I understood it, the scheduler is in a way a robot that just hit's "R"
when t arrives. This seems not to be the case.
Or, the other way round: I had expected, that if the job as such has a
problem it wouldn't reach running status /regardless/ if I hit R
interactively, or the scheduler launches the same thing automatically.
--
Kind regards,
Alexander Wagner
Subject Specialist
Central Library
52425 Juelich
mail : [email protected]
phone: +49 2461 61-1586
Fax : +49 2461 61-6103
www.fz-juelich.de/zb/DE/zb-fi
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
