I have to assume it's something unique to your install, then.
I run about a dozen sshd instances on as many CentOS 7 boxes around here. To a one, systemctl restart sshd is all it takes to implement config changes.
Only time it's given me fits is if I forget to actually write the config file in VIM. That pesky w gets me on rare occasion.
On Thu, Mar 2, 2017 at 11:50 AM, me@tdiehl.org wrote:
Hi,
On Thu, 2 Mar 2017, Tate Belden wrote:
Might I suggest using "systemctl restart sshd", instead of reload? At the
least - see if it behaves differently for you.
restart, reload, stop then start all produce the same results.
If I do not change the configuration, and just issue the restart, reload, etc. then it behaves as expected. Obviously that is not useful when you have configuration changes.
I tested this on a couple of other VM's and get the same results.
Regards,
-- Tom me@tdiehl.org Spamtrap address me123@tdiehl.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos