Request for rabins to handle SIGHUP and reload the config?

[Matt Brown]

Thanks for replying, Carter.

My intention is to specifically change the bin size (by way of
modifying a config file).

I would think it makes sense to:
- allow caches to expire within a max timeout (N seconds.... maybe the
-B ?  maybe the bin size? maybe either as a user wishes?)
- rolling active flows won't be a problem, right?
- Any config changes would take effect after the set expiration.

Do these make sense to you?

I think it makes the most sense to have a single rule ("everything
takes effect after the previous [buffer|bin|whatever] ends"), than to
make seperate rules ("if the bin size changes, then, we will flush
cache after the latest bin expires." and/or "if the output filter
changes, it will be immediate or maybe not.").

But... you know what makes the most sense from what you've seen from
users over the years.


Thanks much,

Matt



On Jan 23, 2014, at 8:01 PM, Carter Bullard <carter at qosient.com> wrote:

> Hey Matt,
> Yes, but there is a lot of behaviors we need to define.
> Do we flush all of the pending data and its caches when we change the configuration, or do we just keep plugging along, and let the caches time out ???  If we change bin sizes, well need to flush everything, if its output filters do they take immediate affect, or after the flush.  There are a lot of issues to consider.
>
> What are you thinking about and what would you like for it to do ??
>
> Carter
>
>> On Jan 23, 2014, at 3:38 PM, Matt Brown <matthewbrown at gmail.com> wrote:
>>
>> Hello all,
>>
>> Carter:  is it possible to add SIGHUP handling to rabins() to reload
>> the config file(s)?
>>
>>
>> Thanks,
>>
>> Matt
>>