### Structure of queue directories ###

<queue>/hosts/<hostname>/	Jobs queued for the given host
				(they are executed in the lexicographic order of <job-id>s)
	/<job-id>.job		Symlink to <queue>/jobs/<job-id>.job
	/<job-id>.stat		(Optional) status of the job
	/<job-id>.tmp		Used temporarily by brun to store the script actually
				sent to the host (can be inspected if something goes wrong)

<queue>/jobs/<job-id>.job	All jobs issued on this queue, including those which
				are no longer queued for any machine

<queue>/log			Log of actions on this queue. Lines look this way:
				YYYY-MM-DD HH:MM:SS <host> <job-id> <status> [<msg>]
				<status> and <msg> correspond to "Status" and "Message"
				in status files.

<queue>/status-fifo		FIFO used for reporting status of subprocesses by `bprun'

### Job files ###

Mail-like structure. First come the headers (<keyword>:<spaces><value>), keywords are
case-sensitive, no multi-line fields allowed, then an empty line and then the body
(i.e., commands to be executed on the remote host).

Known header fields:

ID: <job-id>			Identifier of the job, unique in the scope of a queue
Subject: <subject>		Subject to be displayed to the user

### Status files ###

Structure identical to job headers, but they do not contain a body.

Known fields:

Time: <timestamp>		UNIX timestamp of the last status change
Status: <code>			Machine-readable status of the job:
				NOPING - host does not respond to ping
				NOXFER - transfer of the job body to a temporary file
				     on the host has failed
				OK - job executed successfully (however, the job will
				     be removed from the queue immediately, so you are
				     not likely to see this code)
				FAILED - job failed to execute (i.e., it returned
				         a non-zero exit code)
				INTERR - internal error of BEX
Message: <msg>			(Optional) human-readable message explaining the status