+ [2015-12-22T20:24:15Z] bishop1992 I suspect that something else was using 4000
+ [2015-12-22T20:24:32Z] bishop1992 something was using TCP on 4000
+ [2015-12-22T20:24:57Z] bishop1992 when I reboot next, i'll check to see if the port is still used
+ [2015-12-22T20:31:24Z] parkr bishop1992: ok cool. sometimes other processes use 4000. :)
+ [2015-12-22T20:38:48Z] bishop1992 did some poking around with netstat. 4000 is being used be another process in for my thin client

message no. 123667

Posted by bishop1992 in #jekyll at 2015-12-22T20:22:55Z

parkr. Yes, I found that 4000 was the port. Netstat showed it was already bound. So I used --port 8080 to test and it worked. I updated the _config.yml to use that port
+ [2016-01-09T20:23:39Z] parkr test of irc.parkermoo.re
+ [2016-01-09T20:24:04Z] parkr it works! https://irc.parkermoo.re/messages/123693/context
+ [2016-01-09T20:24:05Z] jekyllrb Title: Chat Log Server / #jekyll (at irc.parkermoo.re)
+ [2016-02-06T00:02:24Z] parkr_ Dry_Lips: re: https://botbot.me/freenode/jekyll/msg/59439748/, it's a problem with jekyll-srcset but it shouldn't break anything https://github.com/netlify/jekyll-srcset/blob/ad7730dea2e3d4e03f8878e2b8fba8123cd06834/lib/jekyll/srcset/tag.rb#L1
+ [2016-02-06T00:02:25Z] jekyllrb Title: jekyll-srcset/tag.rb at ad7730dea2e3d4e03f8878e2b8fba8123cd06834 · netlify/jekyll-srcset · GitHub (at github.com)