Yeah, you can't make me go away by trolling me, insulting me, and lying to me.
I can prove that runit doesn't work.
Or, at least that it doesn't work as documented.# runuser -u ssh-chat -- ssh-chat --verbose --bind=[ip]:[port] --identity=/path/to/chat/server/identity/key/file --motd=/path/to/motd.txt --allowlist=/path/to/allowlist
Added server identity: [redacted]
Listening for connections on [::]:[port]
It runs perfectly. I hit ctrl-c to make it stop. This also works as expected. There are no problems. It is running in the foreground as prescribed by the runit documentation. Clients can connect to the service, via tor and otherwise. There are no problems. It is working perfectly and exactly as it should.
Lets try the /etc/runit/sv/ssh-chat/run file:
# cat /etc/runit/sv/ssh-chat/run
#!/bin/sh
exec chpst -u ssh-chat /path/to/ssh-chat --bind=[ip]:[port] --identity=/path/to/chat/server/identity/key/file --motd=/path/to/motd.txt --allowlist=/path/to/allowlist
# sv start ssh-chat
timeout: down: ssh-chat: 0s, normally up, want up
#
runit has failed to perform a proven and known-working command
I have followed the documentation and done exactly as it prescribes.
Proven: runit doesn't work (as documented).
If there are some undocumented incantations which must be uttered, it would be nice if the documentation were corrected to reflect these (deliberate, obnoxious) omissions.
If you are incapable of anything but name-calling and/or obnoxious, immature nerd trolling; I ask that you do not respond. Do not bugger up the thread with useless brat noise.
I have already noticed that a moderator is observing me and deleting my posts while in preview/edit mode, just like the last thread. Screwing with me for entertainment.