You are not logged in.
hi
just doing a re-install of arch as normal and got a new error - failed to enable ssh.socket. Had a dig around and it seems the socket is not shipped with the main package anymore because of issues, and a general dislike of socket activation. What is the best advice :
- is this correct
- Is this permanent
- should I create a socket activator
- forget it and just enable ssh
- does that create a system overhead
- is it a good idea generally to not have
socket activation
Opinions would be welcome
Olly
Last edited by olly (2019-09-25 12:19:56)
Bullies are only weak people trying to compensate for their own inadequacy. If they can't compete intellectually, they bully.
Offline
Offline
Thanks for reply
Indeed. But what I'm thinking is what is the best thing to do. The issues seem to be caused by an overload of use, whereas on a simple home system this would not be a problem. Either create a socket and avoid the unnecessary overhead of the ssh daemon, or is the overhead negligible and avoiding socket activation the arch philosophy now.
Last edited by olly (2019-09-24 15:38:10)
Bullies are only weak people trying to compensate for their own inadequacy. If they can't compete intellectually, they bully.
Offline