Opened at 2007-09-29T16:27:22Z
Closed at 2007-10-11T10:30:08Z
#156 closed defect (fixed)
how to find tahoe process with ps
| Reported by: | zooko | Owned by: | warner |
|---|---|---|---|
| Priority: | major | Milestone: | 0.6.1 |
| Component: | packaging | Version: | 0.6.0 |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
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).
Change History (2)
comment:1 Changed at 2007-10-11T09:43:27Z by warner
- Owner changed from somebody to warner
- Status changed from new to assigned
comment:2 Changed at 2007-10-11T10:30:08Z by warner
- Resolution set to fixed
- Status changed from assigned to closed
done. I'll create a new ticket (#174) for the $0 stuff.
Note: See
TracTickets for help on using
tickets.
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 .