Groups
Groups
Sign in
Groups
Groups
taskspooler
Conversations
About
Send feedback
Help
Strange results when I use ts from cron
58 views
Skip to first unread message
trtrmitya
unread,
Apr 29, 2009, 9:26:36 AM
4/29/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to taskspooler
Hello!
I setup ts to run 2 jobs at the same time (ts -S 2) and put 3 jobs in
the queue.
ts -l reports:
$ ts -l
ID State Output E-Level Times(r/u/s) Command
[run=2/2]
0 running /tmp/ts-out.kDcG1q sleep
1000
1 running /tmp/ts-out.mgYWr1 sleep
1000
2 queued (file) sleep
1000
If i execute 'ts -l' command from cron (command is running with same
user's credentials)
I get:
ID State Output E-Level Times(r/u/s) Command
[run=0/1]
Looks like ts does not connect to the same socket when run from cron,
but I dont understand why.
Any help will be appreciated.
trtrmitya
unread,
Apr 29, 2009, 9:35:58 AM
4/29/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to taskspooler
Oh sorry forget it.
I am blind or just moron, sorry for the noise :)
Lluís Batlle
unread,
Apr 29, 2009, 10:15:29 AM
4/29/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to tasks...@googlegroups.com
2009/4/29 trtrmitya <
trtr...@gmail.com
>:
>
> Oh sorry forget it.
> I am blind or just moron, sorry for the noise :)
No problem! :)
It may be related to the user id involved, because the default socket
name depends on that user id.
Reply all
Reply to author
Forward
0 new messages