57
|
1 |
System wide queue
|
|
2 |
-------------------------
|
79
|
3 |
You can set the $TS_SOCKET variable to the same name path for all your
|
|
4 |
'ts' processes, and then
|
57
|
5 |
they'll use the same socket for intercommunication. This means - single queue.
|
|
6 |
You should be certain that any 'ts' can read/write to that socket, using
|
79
|
7 |
chmod.
|
|
8 |
|
|
9 |
|
|
10 |
A queue for each resource
|
|
11 |
-------------------------
|
|
12 |
You can use $TS_SOCKET and aliases/scripts for having different queues for
|
|
13 |
different resources. For instance, using bash:
|
|
14 |
alias tsdisk='TS_SOCKET=/tmp/socket.disk ts'
|
|
15 |
alias tsram='TS_SOCKET=/tmp/socket.ram ts'
|
|
16 |
alias tsnet='TS_SOCKET=/tmp/socket.net ts'
|
57
|
17 |
|
|
18 |
|
|
19 |
Be notified of a task finished
|
|
20 |
-------------------------
|
|
21 |
In X windows, inside bash, after submitting the task, I use:
|
|
22 |
$ ( ts -w ; xmessage Finished! ) &
|