Re: getting 'processes:' to fire signals

[mark]

On 30 Apr, Chip Seraphine wrote:
> 
> I'm finding that my 'processes:' section does not send specified signals 
> as often as I think it should.   The signals are sent once in a while 
> (every few hours, apparently), but to ensure them being sent it seems 
> that I need to use the -K flag.  Cfrun seems to ignore the -K option 
> (when running with "cfrun -- -K"), so that is not a practical workaround 
> for my environment (which uses cfrun to instead of cfexecd).    
> 
> Running at -d2 shows that cfagent simply doesn't want to send the 
> signals: "Nothing scheduled for processes.allprocs (0/1 minutes elapsed)".
> 
> What is the mechanism that causes this behavior?  How can I manipulate 
> it to make cfengine more willing to send signals?  This is causing me a 
> lot of grief (things like daemons not being hupped after their config 
> files are tweaked).
> 
> FWIW, I have my ExpireAfter   set to 55; it doesn't seem to matter 
> wether the cfagent is run out of cfservd, cron, or by hand.  


I think you are looking at pass 2 of your execution. If you look
at pass 1 you will see that signals are sent. Unless you are
running cfengine every 30 seconds, you should not see a message
like  (0/1 minutes elapsed) from pass 1. You could set IfElapsed = 0, but that
will leave you vulnerable to other problems, and I don't recommend it.

M

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~