|
57
|
1 |
System wide queue
|
|
|
2 |
-------------------------
|
|
|
3 |
You can set the $USER variable to the same name in all 'ts' processes, and then
|
|
|
4 |
they'll use the same socket for intercommunication. This means - single queue.
|
|
|
5 |
You should be certain that any 'ts' can read/write to that socket, using
|
|
|
6 |
chmod. The current socket naming is:
|
|
|
7 |
/tmp/socket-ts.$USER
|
|
|
8 |
|
|
|
9 |
|
|
|
10 |
Be notified of a task finished
|
|
|
11 |
-------------------------
|
|
|
12 |
In X windows, inside bash, after submitting the task, I use:
|
|
|
13 |
$ ( ts -w ; xmessage Finished! ) &
|
|
|
14 |
|
|
|
15 |
|
|
|
16 |
Add a task to the queue, and receive its output by email (by Raul)
|
|
|
17 |
-------------------------
|
|
|
18 |
It only works if 'ts' outputs the jobid.
|
|
|
19 |
$ id=$(ts sleep 10) && ts -w $id && ts -c $id | mail -s taskend $USER &
|
|
|
20 |
|