Basically every setting one can change about s6-log, since the *-log service scripts will most likely come from the package manager, they should not be edited by the sysadmin.What kind of stuff are you putting in the config file? Is it just atemplate for a logging script?
Since that's the case I will use a config file. Performance was my main concern to be honest.Source your config file in every logger run script you have, andleave the global environment alone. There will be no performance issue.
You mean having a config file for every service, which hosts both the service config and the logger config? That seems like a sensible solution.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.
Thank you. Paul
OpenPGP_0x71C7C85A2EA30F62.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
