Access Keys:
Skip to content (Access Key - 0)
My Area (Access Key - 2)


Toggle Sidebar
Your Rating: Results: PatheticBadOKGoodOutstanding! 0 rates
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Restart the job daemon from the job list

Tags:
Last Updated: Jun 04, 2010 11:44


  • Description

    Does what it says on the tin! If you want to restart the job daemon regularly so that it re-reads the job list, this little script will do the job for you. It's important to restart the job daemon when changing clocks moving from summer to winter time, as otherwise the job daemon will fire off each job twice, an hour apart.


  • Author: Matthew Phillips
  • Additional author(s):
  • Institution: University of Dundee
  • Year: 2009
  • License: BSD style
  • Short description: Use, modification and distribution of the code are permitted provided the copyright notice, list of conditions and disclaimer appear in all related material.
  • Link to terms: [Detailed license terms]
  • Skill required for using this code:
    basic

State

Stable

Programming language

csh

Software requirements

None

Download

Download from http://library.dundee.ac.uk/cgi-bin/services?service=dun-custom-36

Using the following Ex Libris open interfaces

None

Release notes

Please ignore the GNU licence terms distributed in the download. The code is only three lines long and is entirely cribbed from other stuff in $aleph_proc so it's copyright Ex Libris if anything.

Installation instructions

Unpack the tar.gz file, find the p_custom_36 file and place it in your $aleph_proc directory, renaming if you wish. Then use it in the job_list. Does not take any parameters and it doesn't matter which Aleph library batch queue it is called from.

See the ReadMe file in the download for details of how to install prior to Aleph 19.

Known issues

None.


Comments




Page Attachments

No files have been attached to this page.

Added by Matthew Phillips on Nov 30, 2009 11:48, last edited by Matthew Phillips on Jun 04, 2010 11:44

  1. Dec 08, 2009

    This works great!  Thanks Matthew

  2. Dec 09, 2009

    When you restart the job daemon, it is down for a few seconds. Isn't there a risk to miss a job, when you automatically restart the daemon at an "uncontrolled" time?

    1. Dec 09, 2009

      Yes, I guess that is possible, but if you ensure that you restart the job daemon at a time when nothing else is running there shouldn't be a problem. Also, I guess you don't have to run the job through any of the batch queues, and that would guarantee it completes within a few seconds of the time stated in job_list. Jobs which have already been fed into the batch queues by the job manager will not be disrupted by the job manager restarting.

Adaptavist Theme Builder Powered by Atlassian Confluence