From 39f25660714e5640be3dce576a6cfdee9a1672c8 Mon Sep 17 00:00:00 2001 From: Scott Moser Date: Mon, 27 Jul 2015 20:53:44 -0400 Subject: use 'restart' rather than 'reload' on non-systemd systems Testing on trusty shows that: service rsyslog reload does produce a message like: rsyslogd was HUPed but does not result in new config being in honored. Using restart does, and with upstart that should be fine (as upstart will start only if previously running). --- cloudinit/config/cc_rsyslog.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'cloudinit/config') diff --git a/cloudinit/config/cc_rsyslog.py b/cloudinit/config/cc_rsyslog.py index a07200c3..82e382e8 100644 --- a/cloudinit/config/cc_rsyslog.py +++ b/cloudinit/config/cc_rsyslog.py @@ -102,7 +102,7 @@ def reload_syslog(command=DEF_RELOAD, systemd=False): if systemd: cmd = ['systemctl', 'reload-or-try-restart', service] else: - cmd = ['service', service, 'reload'] + cmd = ['service', service, 'restart'] else: cmd = command util.subp(cmd, capture=True) -- cgit v1.2.3