[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]


Bryan Stansell bryan@conserver.com
Fri, 16 Aug 2019 04:05:05 +0000 (UTC)

The answer is a bit complex.  There are a bunch of things that are compared between the old and new console definitions, and the best answer is to look at the source code and see the checks yourself.  Starting here (https://github.com/conserver/conserver/blob/master/conserver/readcfg.c#L2887) you’ll see comparisons that set “closeMatch = 0” - that’s what will trigger a reset.

Hopefully that will help you determine why things are changing.


On Aug 14, 2019, at 1:50 PM, Lonni J Friedman via users <users@conserver.com> wrote:

I'm running conserver-8.2.4, and have a large number of servers with
console sessions being managed by conserver.  Configs change often
(many times/daily), such that I am sending a SIGHUP to the conserver
to keep it aware of all changes.

The man page comments that for a SIGHUP:
changes to consoles are done "in place", resetting the console port
(bringing it down and up) only when necessary.

What defines when the console port needs to be reset?  I'm asking as
I'm seeing ports being reset in a fairly widespread fashion whenever a
SIGHUP is sent, and its unclear why.

users mailing list