Use chronic instead of filtering the output of the stunnel4 init script on restart
authorPaul Wise <pabs@debian.org>
Sun, 30 Nov 2014 08:26:58 +0000 (16:26 +0800)
committerPaul Wise <pabs@debian.org>
Sun, 30 Nov 2014 08:27:19 +0000 (16:27 +0800)
modules/entropykey/manifests/provider.pp

index ea8cb5b..d69ac22 100644 (file)
@@ -11,7 +11,7 @@ class entropykey::provider {
        # our CRL expires after a while (2 or 4 weeks?), so we have
        # to restart stunnel so it loads the new CRL.
        file { '/etc/cron.weekly/stunnel-ekey-restart':
-               content => "#!/bin/sh\n# This file is under puppet control\n# weekly restart of stunnel on ${::hostname}\nenv -i /etc/init.d/stunnel4 restart puppet-ekeyd | grep -vF 'Restarting SSL tunnels: [stopped: /etc/stunnel/puppet-ekeyd.conf] [Started: /etc/stunnel/puppet-ekeyd.conf] stunnel.'\n",
+               content => "#!/bin/sh\n# This file is under puppet control\n# weekly restart of stunnel on ${::hostname}\nenv -i chronic /etc/init.d/stunnel4 restart puppet-ekeyd\n",
                mode    => '0555',
        }