On 15.08.2011 22:26, Jos Groot Lipman wrote: > > First I do a 'fossil ui' on an open checkout. This claims port 8080 (note: > it could also be any other program already using port 8080) > > Next I do a 'fossil winsrv create' and a 'fossil winsrv start' inside > *another* open checkout. This works fine: > Service 'Fossil-DSCM' started. > but no indication about which port is being used. > > http://127.0.0.1:8080 still brings me to the first server started with > 'fossil ui' > Only/If I stop that server, http://127.0.0.1:8080<http://127.0.0.1:8080/> > is suddenly served by the 'Fossil-DSCM' Service (another repository)! Very > confusing. > > Maybe I do not understand Windows services very well but should the 'fossil > server show' command not at the very least show the port it is serving? > > By default, the Windows Service uses port 8080 (this is documented in the help -> fossil help winsrv).
If this port (8080) is already used, the service fails silently. To circumvent this problem either specify a different port when you create the service (-p|--port option) or start the service before you use the "interactive" 'fossil server' or 'fossil ui' commands. HTH -- tsbg _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
