9 Jul
2014
9 Jul
'14
4:34 p.m.
On 07/09/2014 10:50 AM, Mike McCarthy, W1NR wrote:
/usr/sbin/sshd -d seems to work properly and accept connections at the new port. So does typing /usr/sbin/sshd, which daemonizes and runs manually. It now appears that it will not start as a service if I change the port, even after a reboot.
What does 'journalctl -u sshd.service' say?
--
========================================================================
Ian Pilcher arequipeno@gmail.com
Sent from the cloud -- where it's already tomorrow
========================================================================