Thus said Warren Young on Tue, 15 Nov 2016 08:30:56 -0700:
> I'd suggest that if you're going to use ``fossil server'' on a
> permanent basis that you select a much less troublesome port number
> and use the -P option to force it.
It can also be stored as a setting:
$ fossil set
On Nov 15, 2016, at 12:09 AM, J. Cameron Cooper wrote:
>
> after reinstalling [crtmpserver] today I don't see the issue anymore.
It could have been a firewall issue, then, with the package’s post-install
script restoring the proper port 8080 firewall rule, which also allows
>
> On Nov 14, 2016, at 12:32 AM, J. Cameron Cooper wrote:
> >
> > 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
On Nov 14, 2016, at 12:32 AM, J. Cameron Cooper wrote:
>
> 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
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
5 matches
Mail list logo