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
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 al
Thanks for the extensive answer.
Since I feel like we are more and more fighting about each others
wording and the answers consisting of quotations of each other get
longer and longer, I will try and summarize what we have now.
I hope you are fine with this.
My approach(see here: https://sk
Since I was not 100% convinced by Turnstile, I made an attempt on a very
simple alternative way to handle user session tracking.
The (currently very crude) script only runs once on each login and
logout and does the following:
On login:
- Possibly create a /run/session/${USER} directory.
-
