Changes between Version 341 and Version 342 of ippToPsps

Timestamp:

Apr 16, 2012, 9:26:50 AM (14 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -34 +34 @@
  * {{{ssh}}} to a [wiki:ippToPsps_ScratchDatabase#Settingupaloadingmachine loading machine] then run one or more [wiki:ippToPsps#loader.py loader.py] programs to process and publish items that have been queued, like this:'''{{{./run.sh loader.py configName}}}'''
 
-The {{{loader.py}}} instances will now proceed to load all queued data. To monitor and clean-up data, run the following in screen sessions if not already running (these do not need to run on loading machines, and usually run on {{{ipp009}}}):
+The {{{loader.py}}} instances will now proceed to load all queued data. To monitor and clean-up data, run the following in [http://www.manpagez.com/man/1/screen/ screen] sessions if not already running (these do not need to run on loading machines, and usually run on {{{ipp009}}}):
 
  * [wiki:ippToPsps#pollOdm.py pollOdm.py] in order to collect data about the progress of loading through PSPS
@@ -231 +231 @@
 }}}
 
-It is usual to run instances of {{{loader.py}}} in a screen session.
+It is usual to run instances of {{{loader.py}}} in a [http://www.manpagez.com/man/1/screen/ screen] session.
 
 The first thing a {{{loader.py}}} instance does is look to the queue tables in the {{{ippToPsps}}} database for a list of items to process. It first attempts to secure a 'stripe' of RA (from the [wiki:ippToPsps_Database#Thestripetable stripe table]) that is not being processed by any other {{{loader.py}}} clients. If all available stripes have already been reserved, then it chooses the stripe with the largest number of pending items.