Le Wed, May 31, 2023 at 03:54:12AM +0700, Robert Elz a écrit :
> Date: Tue, 30 May 2023 21:03:21 +0200
> From: tlaro...@polynum.com
> Message-ID: <zhzieeeckpwvt...@polynum.com>
>
> | Do you think that SIGINFO is sound as the signal to obtain a config DUMP
> in
> | the syslog?
>
> First, dumping config to syslog seems like an odd thing to do at all, I'd
> normally expect it to be dumped in a file instead (something in /tmp
> perhaps, or where defined in the config file perhaps),
>
> But that's independent of the signal used to make it happen, that
> could be SIGINFO, which normally makes a process list its current
> state (what it is doing) - and for that knowing what config inet is
> serving could be considered part - but that is also typically a lot
> more than SIGINFO generates (usually just a line). Personally
> I'd probably pick a different signal for that, but I am not sure which.
Well, I will go with using SIGUSR1 and SIGUSR2 hence, as Mouse noted,
exhausting the spares.
And I think you're right: the info will go in a 0400 file in /tmp, and
will be a way to obtain various running infos---but for now, just the
running config (it could perhaps be extended, but not now, to add
stats, what is masked by a secmodel etc.)
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
