> Le 27 déc. 2017 à 14:49, Olivier Mascia <o...@integral.be> a écrit : > > On one computer (running Server 2016), I have: > > fossil version -v > This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC > Compiled on Dec 27 2017 13:45:17 using msc-19.11 (64-bit) > > And I can run it as a service. > ... > On another computer (which is 2012 R2), the exact same binary fails to run as > a service. > ... > It is not started because upon attempt to start it, it fails and stops. > Attempting to start it by "fossil winery start fossil" displays dots > endlessly. But I have no clue as to what this happens without any kind of > log of what might go wrong. The Event Viewer simply confirms it started and > then failed to start (or stop). > > Running "C:\Develop\Fossil\fossil.exe" server --repolist "C:/Develop/Fossil" > from a command-line is OK though.
Fun. Fixed. Added -P 8081 to the fossil winsrv create command line. It didn't occurred to me immediately, but when ran from command-line the web service exposed itself from port 8081 and not 8080. So I suspected that maybe in service mode it might not auto-correct the port (8080 is indeed occupied by another software on *that* machine). Bingo. -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
