On Thu, 2 Mar 2017, Tate Belden wrote:
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.
Did you actually change something before doing the restart? If nothing changes
it will restart every time. If I change the configuration to for instance have
sshd listen on another port, that is when I have the problem. Oh and selinux is
in permissive.
There is nothing special about the environment. a couple of VM's in question
are brand new minimal installs. I spin them up for testing push new sshd configs
to them with Ansible and tear them down.
Before someone says Ansible is the problem I have tried this by hand also.
Regards,
--
Tom me@xxxxxxxxxx Spamtrap address me123@xxxxxxxxxx
On Thu, Mar 2, 2017 at 11:50 AM, <me@xxxxxxxxxx> 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.
--
Tom me@xxxxxxxxxx Spamtrap address me123@xxxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
