Issue #4624 has been reported by eric sorenson.
----------------------------------------
Bug #4624: SIGUSR1 should ignore splay
http://projects.puppetlabs.com/issues/4624
Author: eric sorenson
Status: Unreviewed
Priority: Normal
Assignee:
Category: agent
Target version:
Affected version: 0.25.5
Keywords: splay signal usr1
Branch:
When testing whether I could trigger an immediate run to a running puppetd, I
found I could not. I can understand HUP (restart) simply causing a from-the-top
restart of execution, but it surprised me that USR1 (reload) behaved the same.
IMO if I'm actively sending a reload signal to the daemon, I'd like it to take
action immediately, not restart the splay timer.
{{{
notice: Starting Puppet client version 0.25.5
info: Sleeping for 902 seconds (splay is enabled)
[1]+ Stopped puppetd --no-daemonize --debug
[r...@pt-linux17 /etc/rc.d/init.d]# killall -USR1 puppetd
[r...@pt-linux17 /etc/rc.d/init.d]# fg
puppetd --no-daemonize --debug
notice: Caught USR1; calling reload
info: Sleeping for 179 seconds (splay is enabled)
[1]+ Stopped puppetd --no-daemonize --debug
[r...@pt-linux17 /etc/rc.d/init.d]# killall -USR1 puppetd
[r...@pt-linux17 /etc/rc.d/init.d]# fg
puppetd --no-daemonize --debug
notice: Caught USR1; calling reload
info: Sleeping for 1366 seconds (splay is enabled)
}}}
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
