> And why sighup? Shouldn't just limiting sec be enought. SIGHUP has many
> side effects. I don't think we should trigger these for connection time.
> 
> 
> With default setting this results in a SIGHUP after some hours and also
> the last intervals with 5120s are too big for default settings. I would
> aim for something lower like five or ten minutes.

I think a bit about that and I think a good way to specify exponential
back is something like

connect-retry 5 1800, which would mean "scale back up to 1800s" and
maybe default that option to connect-retry 5 300. That also allows
specifying larger connect-retry values without backoff. E.g.
connect-retry 60 60

Arne


Reply via email to