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:
# 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
Does anyone know why those systemd configuration files got lost after system installation? I couldn't find any explanation for this...
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.
On Sat, 10 Aug 2024 11:43:15 -0700 Samuel Sieb samuel@sieb.net 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 Hanzlík via users wrote:
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...
These files are marked %ghost to prevents them from being removed *if they existed and were modified* prior to commit 4c7acde (Do not remove modified config files, 2023-12-13)¹ on the f40 branch of the systemd package.
¹ https://src.fedoraproject.org/rpms/systemd/c/4c7acde
I wrote:
These files are marked %ghost to prevents them from being removed *if they existed and were modified* prior to commit 4c7acde (Do not remove modified config files, 2023-12-13)¹ on the f40 branch of the systemd package.
And perhaps I should have also noted the earlier commit which moved them from /etc to /usr/lib, 29eb355 (Move config files to /usr/lib/systemd, 2023-12-08)¹.
¹ https://src.fedoraproject.org/rpms/systemd/c/29eb355
On Sat, 10 Aug 2024 15:27:05 -0400 Todd Zullinger tmz@pobox.com wrote:
I wrote:
These files are marked %ghost to prevents them from being removed *if they existed and were modified* prior to commit 4c7acde (Do not remove modified config files, 2023-12-13)¹ on the f40 branch of the systemd package.
And perhaps I should have also noted the earlier commit which moved them from /etc to /usr/lib, 29eb355 (Move config files to /usr/lib/systemd, 2023-12-08)¹.
¹ https://src.fedoraproject.org/rpms/systemd/c/29eb355
Hi Todd, thanks you for the info, that explains it all. This Fedora 40 Server was new installation - and the reason I still have those files on my desktop is because its Fedora 40 is there via 'dnf system-upgrade' - and those /etc/systemd/*.conf files are apparently from the previous Fedora 38...
-
Franta Hanzlík -
Samuel Sieb -
Todd Zullinger