how to find tahoe process with ps #156

Closed
opened 2007-09-29 16:27:22 +00:00 by zooko · 2 comments
zooko commented 2007-09-29 16:27:22 +00:00
Owner

Sebastian tried Tahoe last night, and after it said "client node probably started" (#71), then he ran some command-line like

ps eauwx | grep tahoe

And, seeing no output, he believed that the node hadn't started. It would be arguably good if the actual $0 program name were "allmydata-tahoe", but if that's too hard or has other drawbacks, perhaps we just just renamed client.tac to allmydata-tahoe.tac. Then the grep would find it (unless the user's terminal were too narrow).

Sebastian tried Tahoe last night, and after it said "client node probably started" (#71), then he ran some command-line like ``` ps eauwx | grep tahoe ``` And, seeing no output, he believed that the node hadn't started. It would be arguably good if the actual $0 program name were "allmydata-tahoe", but if that's too hard or has other drawbacks, perhaps we just just renamed client.tac to allmydata-tahoe.tac. Then the grep would find it (unless the user's terminal were too narrow).
tahoe-lafs added the
packaging
major
defect
0.6.0
labels 2007-09-29 16:27:22 +00:00
tahoe-lafs added this to the 0.6.1 milestone 2007-09-29 16:27:22 +00:00
warner commented 2007-10-11 09:43:27 +00:00
Author
Owner

Yeah, I'd prefer to have $0 be 'tahoe' or equivalent, but that would
dramatically change the way we launch twistd. It's possible.. I'm doing it in
buildbot, and the resulting argv looks like ('/usr/bin/python',
'/usr/bin/buildbot', 'start', '/usr/home/buildbot/petmail/master'). But it
requires us to launch twistd as a python function (internally), rather than
through os.system, and that requires some serious fiddling that I don't want
to mess with before 0.6.1 .

Renaming the .tac file is a good start, though. I think we need some
backwards compatibility for all the existing nodes, though. I'll make it look
for either client.tac or tahoe-client.tac, and make create-client make
tahoe-client.tac .

Yeah, I'd prefer to have $0 be 'tahoe' or equivalent, but that would dramatically change the way we launch twistd. It's possible.. I'm doing it in buildbot, and the resulting argv looks like ('/usr/bin/python', '/usr/bin/buildbot', 'start', '/usr/home/buildbot/petmail/master'). But it requires us to launch twistd as a python function (internally), rather than through os.system, and that requires some serious fiddling that I don't want to mess with before 0.6.1 . Renaming the .tac file is a good start, though. I think we need some backwards compatibility for all the existing nodes, though. I'll make it look for either client.tac or tahoe-client.tac, and make create-client make tahoe-client.tac .
warner commented 2007-10-11 10:30:08 +00:00
Author
Owner

done. I'll create a new ticket (#174) for the $0 stuff.

done. I'll create a new ticket (#174) for the $0 stuff.
tahoe-lafs added the
fixed
label 2007-10-11 10:30:08 +00:00
warner closed this issue 2007-10-11 10:30:08 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#156
No description provided.