Hi Leah, > My assumption was there was a runaway instance of socat running (for > unknown reasons), and I decided to kill all socat instances. My usual > tool of choice would have been `killall socat`, but as there were other > socat instances running on the machine, I only wanted to kill the port > 3722 ones. > > Lessons learned: > - The first intuition is often right, even if it's not plausible at first. > - Don't use `pkill -f` as root, at least not without careful checking > and regexp anchoring. > - If a box doesn't react to reset requests, try sending wake-on-lan to > turn it on. > - runit should reboot by default, not shutdown!
Or track the origin of the issue (runaway socat instance), did you find anything? -- You received this message because you are subscribed to the Google Groups "voidlinux" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/20190215091115.1444c0c7%40fifth.space. For more options, visit https://groups.google.com/d/optout.
