how to find tahoe process with ps #156
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#156
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sebastian tried Tahoe last night, and after it said "client node probably started" (#71), then he ran some command-line like
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).
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 .
done. I'll create a new ticket (#174) for the $0 stuff.