On Sat, 10 Aug 2024 11:43:15 -0700 Samuel Sieb <samuel@xxxxxxxx> wrote: > On 8/10/24 11:22 AM, Franta Hanzlík via users wrote: > > My actual problem is other: I want somehow debug program (ISC bind > > daemon) crashes. And I'm trying to figure out why abrt doesn't create > > a crashdump in /var/spool/abrt/ directory after I install the debuginfo > > package - although it did before... > > > > I had an idea that some limits for systemd-coredump might need to be > > increased. But I'm surprised and I can't explain why the configuration > > files of the systemd daemon are completely missing in the system - those > > under the /etd/systemd/ directory (system.conf, user.conf, logind.conf, > > journald.conf, etc.}. Under /etd/systemd/ I have only network, system > > and user subdirs, but no ordinal file - although in packages these > > should be: > > The place for system provided file is /usr/lib/systemd > /etc/systemd is for user overrides. > > > # rpm -ql systemd|grep -E '/etc/systemd/[^/]+\.conf$' > > /etc/systemd/journald.conf > > /etc/systemd/logind.conf > > /etc/systemd/system.conf > > /etc/systemd/user.conf > > > > and is weird, the systemd package verification will take place without > > errors (as if those .conf files are optional?!): > > > > # rpm -V systemd; echo "RES=$?" > > RES=0 > > > > The verbose verification lists them as missing, but the rpm exit status > > is also 0: > > # rpm -Vv systemd|grep -E '/etc/systemd/[^/]+\.conf$' > > missing c /etc/systemd/journald.conf > > missing c /etc/systemd/logind.conf > > missing c /etc/systemd/system.conf > > missing c /etc/systemd/user.conf > > Those are marked in the rpm as config files so the package still owns > them, but they are not included in the rpm and are only created if the > user does it. It is not a verification error for config files to be > missing. > > > Does anyone know why those systemd configuration files got lost after > > system installation? > > I couldn't find any explanation for this... > > They aren't lost. They never existed. > -- Hello Samuel, thanks for explanation. I was confused by the fact that so far, during the entire systemd era, since Fedora 15, i had these /etc/systemd/*.conf files present in the system. And I also lived in the fact that it is not enough for the package file to be marked as config - for the verification to pass if it is missing. I thought they must have some "phantom" attribute or something similar. I have to look into it more closely... -- Franta Hanzlik -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
