#185 closed defect (fixed)
default settings can't run two nodes on the same computer
| Reported by: | zooko | Owned by: | zooko |
|---|---|---|---|
| Priority: | major | Milestone: | 0.7.0 |
| Component: | code-frontend | Version: | 0.6.1 |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
The default settings run a webport, and try to bind to port 8123, so the second node so started fails to start.
To fix this bug we could:
a) make it run no webport by default b) make it attempt to run a webport but start anyway if it can't c) make it get a different port number if 8123 is occupied
other ?
Change History (6)
comment:1 Changed at 2007-10-18T19:04:07Z by zooko
- Milestone changed from undecided to 0.6.2
comment:2 Changed at 2007-10-21T09:20:22Z by warner
comment:3 Changed at 2007-10-22T22:52:21Z by warner
er, that's --webport=none, or --webport none, or -p none.
comment:4 Changed at 2007-10-22T23:09:13Z by zooko
- Owner set to zooko
- Status changed from new to assigned
Yeah, I think I agree. The default values of the params are for a single-user machine, and for the kind of user who wants one node. If you want multiple nodes on your machine, or you are sharing a machine with other users, then you'll have to learn how to configure webport yourself.
comment:5 Changed at 2007-10-23T01:10:55Z by zooko
- Resolution set to fixed
- Status changed from assigned to closed
Fixed by e992fed1f53ba27c.
comment:6 Changed at 2007-11-01T18:12:49Z by zooko
- Milestone changed from 0.6.2 to 0.7.0
Milestone 0.6.2 deleted
Note: See
TracTickets for help on using
tickets.
d) document that if you want to do this, you must pass 'p none' to all but one of them, to disable the webport.
I suspect that we will either be able to cleanly support an easy single-node everything-gets-set-up-for-you case, or multiple nodes, but not both..