Added the web page. v0.4.1
Mon, 12 Nov 2007 09:57:46 +0100
changeset 140 0b99d94818d1
parent 139 e5c0fccdb233
child 141 b0e29c0c118e
Added the web page.
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/web/index.html	Mon Nov 12 09:57:46 2007 +0100
@@ -0,0 +1,108 @@
+<html lang="en">
+	<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+	<title>Task Spooler - batch is back!</title>
+<h1>Task Spooler</h1>
+<p>I wrote <em>Task Spooler</em> because I didn't have any comfortable way of
+running batch jobs in my linux computer. I wanted to:</p>
+<li>Queue jobs from different terminals.
+<li>Use it locally in my machine (not as in network queues).
+<li>Have a good way of seeing the output of the processes (tail, errorlevels,
+<li>Easy use: almost no configuration.
+<li>Easy to use in scripts.
+<p>You can look at an old (but representative)
+<a href="ts-0.2.1.png">screenshot</a> if you want.</p>
+<h2>Mailing list</h2>
+<p>Alessandro Öhler prepared a mailing list for discuting newer functionalities
+and interchanging use experiences. You can look at the
+<a href="">archive</a> or
+<a href="">subscribe</a>.
+<h2>How it works</h2>
+<p>The queue is maintained by a server process. This server process is started
+if it isn't there already. The communication goes to a unix socket in
+<p>When the user requests a job (using a ts client), the client waits for the
+server message to know when it can start. The client usually forks, but
+it will run the command with the proper environment, because
+<em>the client</em> will
+run the job (not the server, like in 'at' or 'cron'). So, the ulimits,
+environment, pwd,. apply.</p>
+<p>When the job finishes, the client notifies the server. At this time,
+the server may notify any <em>waiting</em> client, and stores the 
+output and the errorlevel of the finished job.</p>
+<p>Download the latest version (GPL licensed):
+<a href="ts-0.4.1.tar.gz">ts-0.4.1.tar.gz</a> - v0.4.1</p>
+<p>Look at the
+<a href="/~mercurial/cgi-bin/hgwebdir.cgi/ts">version repository</a> if you are
+interested in its development.</p>
+<p>Андрей Пантюхин (Andrew Pantyukhin) maintains the
+<a href="">BSD port</a>.</p>
+<p>Alessandro Öhler provided a Gentoo
+<a href="ts-0.4.ebuild">ebuild for .10.4</a>.</p>
+<p>Look at its <a href="man_ts.html">manpage</a> (v0.4).
+Here you also have a copy of the help for the same version:</p>
+usage: ts [action] [-n] [-f] [cmd...]
+Env vars:
+  TS_SOCKET  the path to the unix socket used by the ts command
+  TS_MAILTO  where to mail the result (on -m). Local user by default
+  TS_MAXFINISHED  maximum finished jobs in the queue
+  TS_ONFINISH  binary called on job end (passing jobid, error, outfile, command)
+  -K       kill the task spooler server
+  -C       clear the list of finished jobs
+  -l       show the job list (default action)
+  -t [id]  tail -f the output of the job. Last if not specified.
+  -c [id]  cat the output of the job. Last if not specified.
+  -p [id]  show the pid of the job. Last if not specified.
+  -o [id]  show the output file. Of last job run, if not specified.
+  -s [id]  show the job state. Of the last added, if not specified.
+  -r [id]  remove a job. The last added, if not specified.
+  -w [id]  wait for a job. The last added, if not specified.
+  -u [id]  put that job first. The last added, if not specified.
+  -U &lt;id-id&gt;  swap two jobs in the queue.
+  -h       show this help
+  -V       show the program version
+Options adding jobs:
+  -n       don't store the output of the command.
+  -g       gzip the stored output (if not -n).
+  -f       don't fork into background.
+  -m       send the output by e-mail (uses sendmail).
+<li>To Raúl Salinas, for his inspiring ideas
+<li>To Alessandro Öhler, the first non-acquaintance user, who proposed and
+created the mailing list.
+<li>Андрею Пантюхину, who created the <em>BSD port</em>.
+<li>To the useful, although sometimes uncomfortable, UNIX interface.
+<li>To GNU, an ugly but working and helpful ol' UNIX implementation.
+<a href="">Lluís Batlle i Rossell</a>,