move setup work to "before the fork" in the cli #2139

Closed
opened 2013-12-19 16:29:57 +00:00 by zooko · 1 comment

As Brian suggested in comment:70118, it would be nice if more of the setup work were done before the fork, or even better if the fork were removed entirely. The reason it is a problem to do the setup work after the fork is that then an exception during the setup work appears in the log file but is invisible to the CLI.

As Brian suggested in [comment:70118](/tahoe-lafs/trac-2024-07-25/issues/649#issuecomment-70118), it would be nice if more of the setup work were done before the fork, or even better if the fork were removed entirely. The reason it is a problem to do the setup work after the fork is that then an exception during the setup work appears in the log file but is invisible to the CLI.
zooko added the
code-frontend-cli
normal
enhancement
1.10.0
labels 2013-12-19 16:29:57 +00:00
zooko added this to the undecided milestone 2013-12-19 16:29:57 +00:00

"tahoe start", the daemonizing startup command, is now deprecated. Thus, there is no longer a non-deprecate fork-using startup command. Thus, the fork has essentially been removed.

"tahoe start", the daemonizing startup command, is now deprecated. Thus, there is no longer a non-deprecate fork-using startup command. Thus, the fork has essentially been removed.
exarkun added the
was already fixed
label 2020-01-20 20:36:18 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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