Enhancement: allow job accounting info to be logged to an accounting logfile (= gatekeeper logfile by default). See corresponding patch to the gatekeeper itself. For each job, the accounting information is of the following format: ---------------------------------------------------------------------- JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID for on JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID has GRAM_SCRIPT_JOB_ID \ manager type JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID JM exiting ---------------------------------------------------------------------- The string has this format: YYYY-MM-DD.HH:MM:SS.. where and are left-padded with zeroes to have 10 digits. is the PID of the gatekeeper, is request sequence number (incremented per connection). The string is obtained from the "GATEKEEPER_JM_ID" environment variable defined by the gatekeeper (see corresponding patch for the gatekeeper). The second JMA line allows the job's and originating host to be linked to the job's accounting information recorded by the batch system. A corresponding patch for the LSF job manager script supplies a job summary before the "JM exiting" line, of the following format: ---------------------------------------------------------------------- JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID summary: "> JMA -- end of summary ---------------------------------------------------------------------- For other batch systems such a job summary is not yet available. The accounting information is written to the file descriptor named by the "GATEKEEPER_ACCT_FD" environment variable defined by the gatekeeper (see gatekeeper patch); if the variable is not set, or if the descriptor cannot be written to, the accounting information is discarded. Finally, this patch also arranges for job info to be written to an extra file in the GASS cache, allowing for easier cleanup of stale jobs. By LCG (David.Smith@cern.ch, Maarten.Litmaath@cern.ch).