El 2022-11-30 15:53, Adam Tuja escribió:
it's a concept - either one supports configuration management, or
one
doesn't.
Out of curiosity. Wouldn't it make sense if program used more
configuration fes?
And what's the difference between, for example?
/etc/sensors
And
/etc/sensors.d
Or
Normally /etc/subdirectory.d is used by software that uses several
configuration files, it can be one or more. Usually it holds more than
one.
/etc/cron.d
And
/etc/cron.daily
/etc/cron.weekly
/etc/cron.monthly
Why aren't these directories subdidirectories of /etc/cron or
/etc/cron.d for that matter?
From `man cron`
"
Additionally, in Debian, cron reads the files in the /etc/cron.d
directory. cron treats the files in
/etc/cron.d as in the same way as the /etc/crontab file (they
follow the special format of that file, i.e.
they include the user field). However, they are independent of
/etc/crontab: they do not, for example, in‐
herit environment variable settings from it. This change is
specific to Debian see the note under DEBIAN
SPECIFIC below.
"
This depends on the implementation of the cron system, as I see it seems
they are using "Vixie Cron", which supports sending mails through the
daily cron instances. Hence they have added the control for environment
variables for the cron daemon initialization, in order to control
certain environment variables (LANG, LC_CTYPE, ...) in order to set the
charset for the mails.
There are cron implementations that do not support sending mails by
definition of their own design, instead I understand that it can be
configured from the configuration file to send mails (as an external
thing).
