Re: what is normal conserver hang during reconfig

Running v 8.1.18.  Rereading the SIGHUP section of the man page I'm
still thinking I've configured something wrong.  SIGHUP says conserver
rereads the config files and then adds/deletes consoles as needed and
only touches running consoles if they have changed.  If thats true I
wouldn't expect a 30s buffer of input/output on a console that hasn't
changed, should I?
I also don't see anything in CHANGES that sounds like this is a bug
that has been fixed.

-denis

On Fri, Oct 14, 2016 at 12:05:44PM -0400, Denis Hainsworth wrote:
> I love conserver.  I have  a minor issue and I was curious what options
> there might be.
> 
> So I have a conserver setup running against 262 servers (mostly digis or
> ser2net machines).  It works great.  However when we need to update due
> to a config change we run "kill -HUP" against the parent.  With the
> number of consoles (I think) this causes about a 30s "hang" when
> interacting with any console which corresponds to the reconfig time.
> 
> Does this make sense and is per the current design?  Any chance there is
> a clever way to make it block for less time?  Barring that I intend to
> spin up a new server to share the load of my current server and reduce
> the reconfig time.
> 
> I was mostly curious if there was a config issue or if this description
> doesn't make any sense to folks and it means I have something else going
> on like too many down consoles or something.
> -denis
> 
> -- 
> __________________________
> Denis Alan Hainsworth     
> denis.hainsworth@gmail.com

-- 
__________________________
Denis Alan Hainsworth     
denis.hainsworth@gmail.com