Am 19.03.2015 um 19:36 schrieb Andy Bradford:
Thus said Tontyna on Thu, 19 Mar 2015 11:58:40 +0100:
Starting several fossil servers with "ui" increments port from 8080 onwards.
Starting several fossil servers with "server" increments port ditto.
Mixing "ui" and "server" instances results in double-bound ports.
Don't know whether that's a Windows-only issue.
This is not a Windows-only behavior. The server does not use any
specific IP and in fact uses any (0.0.0.0) as shown in your netstat
output. Whereas ui wants to be on 127.0.0.1 to restrict access to the
local machine only. 127.0.0.1 is more specific, so your OS allows it
(OpenBSD allows it to). There is no double-binding going on here. If you
had 10 IP addresses you could have 10 things all listening on port 8080.
If you point your browser to 127.0.0.1:8080 you'll get the UI instance.
If you point your browser to 192.168.1.10:8080 (or whatever your IP
happens to be) I imagine you'll get the server.
Andy
--
TAI64 timestamp: 40000000550b1748
Thank you very much for your explanation.
From now on I'll use "http://localhost"; to display repos served by
`fossil ui` and "http://computername"; to request from `fossil server`.
To avoid confusion in the browser (refresh a page with an URL/port that
in the meanwhile points to another repo) I could apply clear-cut
distinct stylings to my repos.
- Tontyna
P.S.: The mixed-up communication (aka double-bind) at work involved a
server computer having multiple IPs. Will definitely recheck that.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
