Re: [fossil-users] new winsrv command: which port does it use?

2011-08-17 Thread Nathaniel R. Reindl
On 16 Aug 2011, at 12:14, Stephan Beal wrote: > _Almost_ analogous - in Unix we have grep /var/log/... at our > disposal, but > on Windows we're screwed. ("We" = Windows users, not me.) Windows has the Event Viewer, which can be accessed by invoking `eventvwr.msc` in either a cmd.exe window or t

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Stephan Beal
On Tue, Aug 16, 2011 at 7:01 PM, Nathaniel R. Reindl wrote: > This is analogous to configuring a service on a UNIX box and then having > to dig through the logging information to determine the root cause when > it fails to come up, no? :) _Almost_ analogous - in Unix we have grep /var/log/... at

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Nathaniel R. Reindl
On 16 Aug 2011, at 11:31, Stephan Beal wrote: > On Tue, Aug 16, 2011 at 6:11 PM, Thomas Schnurrenberger > wrote: > >> easily communicate with the logged in user, if any. If the service >> would select the TCP port by himself, how to inform the user? > > > LOL! How true. The moral of the story, it

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Jos Groot Lipman
-Original Message- >> If the service would select the TCP port by himself, how to inform the user? There is no way to 'push' a message but fossil winsrv show Could show it? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org ht

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Stephan Beal
On Tue, Aug 16, 2011 at 6:11 PM, Thomas Schnurrenberger wrote: > easily communicate with the logged in user, if any. If the service > would select the TCP port by himself, how to inform the user? LOL! How true. The moral of the story, it seems, is that sometimes features which seem to be dumb at

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Thomas Schnurrenberger
On 16.08.2011 17:20, Stephan Beal wrote: > On Tue, Aug 16, 2011 at 5:03 PM, Thomas Schnurrenbergerwrote: > >> 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

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Konstantin Khomoutov
On Tue, 16 Aug 2011 17:20:08 +0200 Stephan Beal wrote: > > 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" '

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Stephan Beal
On Tue, Aug 16, 2011 at 5:03 PM, Thomas Schnurrenberger wrote: > 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" 'f

Re: [fossil-users] new winsrv command: which port does it use?

2011-08-16 Thread Thomas Schnurrenberger
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 f

[fossil-users] new winsrv command: which port does it use?

2011-08-15 Thread Jos Groot Lipman
I have compiled the latest trunk-version with the new winsrv command to test it. It leaves me slightly confused to which port Fossil uses this way. 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