On Dec 19, 2017, at 1:49 PM, Warren Young <war...@etr-usa.com> wrote:
>
> If it’s a sign of a bug, then it means something very bad has happened, like
> the network stack has lost track of its client somehow. To see that, you’d
> need to do a network capture on that fossil instance’s network sockets. Use
> netstat -nap or lsof -i to find out which TCP ports those are.
Something else which might be helpful is the output of:
$ netstat -na | grep :80
That’s assuming Fossil listens on TCP port 80 on your system. If not, adjust
to suit.
This possibly-relevant and certainly-fascinating article just popped up on
Reddit recently:
https://blog.cloudflare.com/this-is-strictly-a-violation-of-the-tcp-specification/
TCP can do some really strange things in the corner cases.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
