I've been happily using fossil for quite a few years now, but I recently
had an unusual symptom develop on one of my machines. I think it's a bug,
but I have no idea how to add a ticket on the main site, so I'll drop it
here.

I found the command 'fossil server' caused fossil to spin with 100% cpu
usage (for at least hours, so I'm guessing it's indefinite) when it tried
to listen on the default port if that port was already occupied by
'crtmpserver'. (For most occupants of a port fossil prints out a message
about the conflict and exits, but for 'crtmpserver' it just sits and spins
as described. Perhaps 'crtmpserver' is poorly behaved?)

It's not a popular package, but perhaps the condition may be exercised by
other daemons as well, so I thought it worth reporting. crtmpserver may
have just started running on 8080 via an update; dunno why else I suddenly
encountered this.

OS is Linux Mint 17.3. Fossil version is 1.35, though the same occurs on
1.27 (the distro version). The 1.35 version prints "Listening for HTTP
requests on TCP port 8080"; the 1.27 prints nothing. 'fossil ui' behaves
similarly.

-- 
J Cameron Cooper
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to