You are not logged in.
hi
i was studying any man-pages and articles on arch wiki about systemd and journald including journalctl with journald.conf.
thereafter i adjusted some parameter values to the system needs (MaxRetentionSec=1day; MaxFileSec=1month). worked out well - but ...
now there are two open questions:
- when do which changes take effect?
in some documentations it is mentioned ... takes effect after reboot, restart service, reload service ..
there is a defined file-chain ... which available files are loaded in which order?
- what parameters are loaded actually? (used <systemctl status unit> and <journalctl -u unit>)
there is a defined file-chain ... which file[s] [is|are] actual loaded?
which are the actual loaded parameters?
what documentation did i miss? actually i do feel runnig blind. do you trace the units in the kernel?
Last edited by SwissGeorge (2017-07-10 04:45:02)
Offline
Welcome to the arch linux forums SwissGeorge.
- when do which changes take effect?
in some documentations it is mentioned ... takes effect after reboot, restart service, reload service ..
Please define exactly what changes you are referring to you mention journald.conf in the case of a configuration file for a particular binary reboot and restart should always reread that binaries configuration.
For reload it depends if the .service contains an ExecReload entry indicating reload support.
there is a defined file-chain ... which available files are loaded in which order?
Load order for what?
- what parameters are loaded actually? (used <systemctl status unit> and <journalctl -u unit>)
there is a defined file-chain ... which file[s] [is|are] actual loaded?
which are the actual loaded parameters?
See man 5 systemd.unit
Offline
thank you for answer logs. i do learn not being precisly enough. sorry for wasting your time.
Please define exactly what changes you are referring to you mention journald.conf
i was mentioning (MaxRetentionSec=1day; MaxFileSec=1month) but did not mention in file /etc/systemd/journald.conf.
systemd.service describe ExecReload a cmd which is not implemented in journald. no documention of journald does not document how to load its configuration correctly. let me know please if i'm wrong.
so you can try a systemctl [start & stop | restart] systemd-journald.service. that's what id and mentioned <worked well>.
Load order for what?
context is journald.conf. i was not clear. documented is a chain configuration files in journald.conf: /etc/systemd/journald.conf:/etc/systemd/journald.conf.d/*.conf:/run/systemd/journald.conf.d/*.conf:/usr/lib/systemd/journald.conf.d/*.conf. there is a nice section <Unit File Load Path> in systemd.unit man page describing the load of binary files, the service it self. i was looking for similar description for chainloading the configuration for systemd-journald.service. it is not documented. let me know please if i'm wrong.
this lead to the question what are the values in the running service serviced-journald.service? my experience showed many times ... is not as expected MaxRetentionSec=1day and MaxFileSec=1month unless i see it somewhere .. log or service output. was looking for something alike --dump-configuration-items but for systemd-journald.
in a running system are hundreds of services activ each one driven by configuration values. if your system is misbehaving. how do you get to the cause? that's not the question to answer. it just show my background of this thread. that's the motivation for <running blind>. if ever someone is not runnig his system blind. how to?
i'm going to move this subject over to freedesktop.org. it might be of topic here.
thank you anyway
Offline
i was looking for similar description for chainloading the configuration for systemd-journald.service. it is not documented. let me know please if i'm wrong.
When packages need to customize the configuration, they can install
configuration snippets in /usr/lib/systemd/*.conf.d/. Files in /etc/
are reserved for the local administrator, who may use this logic to
override the configuration files installed by vendor packages. The main
configuration file is read before any of the configuration directories,
and has the lowest precedence; entries in a file in any configuration
directory override entries in the single configuration file. Files in
the *.conf.d/ configuration subdirectories are sorted by their filename
in lexicographic order, regardless of which of the subdirectories they
reside in. If multiple files specify the same option, the entry in the
file with the lexicographically latest name takes precedence. It is
recommended to prefix all filenames in those subdirectories with a
two-digit number and a dash, to simplify the ordering of the files.To disable a configuration file supplied by the vendor, the recommended
way is to place a symlink to /dev/null in the configuration directory
in /etc/, with the same filename as the vendor configuration file.
Edit You need to distinuish between the configuration for the service file systemd-journald.service which you already agree you found the precedence rules for
and the precendence rules for the configuration for the binary systemd-journald.
Last edited by loqs (2017-05-05 12:42:53)
Offline