The disadvantage of such an approach is that it requires an active user to be logged in, so if he wants to start using "fossil server" instead of "fossil ui" (perhaps he wants to access his fossil service from another machine at some point, or have a friend/coworker help with development...), then he'll have to be logged in to allow the fossil server to respond to requests. That might be fine during business hours, but what if he goes on vacation, or if the machine is rebooted by Windows Update or the network admin?
What's really needed is a service-oriented solution like NSSM. On Thu, Jul 14, 2011 at 1:59 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Thu, 14 Jul 2011 12:16:37 -0400 > Tomek Kott <tkott.s...@gmail.com> wrote: > > > in cygwin the same commands work > > > > Windows command line you can do "start fossil ui", but this also > > creates a separate console window, which doesn't help you. It does > > appear differently in the taskbar however: a icon-less application, > > rather than a command line icon. > [...] > > One can use the cmdow [1] freeware tool which is kind of "start on > steroids"; for instance, to run `fossil ui` hidden one could do > > cmdow /RUN /HID fossil ui > > To kill a (hidden) running fossil instance one could use > > taskkill /f /im fossil.exe > > This is a built-in since XP, IIRC. > > 1. http://www.commandline.co.uk/cmdow/ > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
