s6/s6-rc policy for Gentoo: logging settings

s6/s6-rc policy for Gentoo: logging settings

[Paul Sopka]

[-- Attachment #1.1.1: Type: text/plain, Size: 684 bytes --]

I have another basic decision to make, on which I am interested to hear 
everybody's opinion.

Should every s6-log daemon have it's own config file or shall they all 
share one?

My initial instinct on this was to put the global logging settings into 
the env directory of s6-linux-init to have all of them available to 
every logging daemon.

This would remove the overhead of having each of the s6-log scripts 
source a config file.

Is there any general issue with the global env's from s6-linux-init's 
env directory, which makes sourcing the same config file in every s6-log 
script a better choice for a global config?


Thank you for your input.


Paul


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: s6/s6-rc policy for Gentoo: logging settings

[Laurent Bercot]

>Should every s6-log daemon have it's own config file or shall they all share one?

  What kind of stuff are you putting in the config file? Is it just a
template for a logging script?


>Is there any general issue with the global env's from s6-linux-init's env directory, which makes sourcing the same config file in every s6-log script a better choice for a global config?

  The global environment defined in s6-linux-init applies to *all*
processes in the system. It's not nice to pollute it with stuff that
would only apply to a pretty restricted subset of all the processes
on the machine.

  Source your config file in every logger run script you have, and
leave the global environment alone. There will be no performance issue.

  For more configurability, you could e.g. have a default logging 
template
hardcoded in your run scripts, that you could override via a service-
specific configuration file.

--
  Laurent