[opensuse-packaging] Ownership of runtime data
Hallo, I've found that we are not consistent in a fact if package should own files with a runtime data or not. Simple check on my factory system says # rpm -qf /run/* file /run/acpid.pid is not owned by any package file /run/acpid.socket is not owned by any package file /run/auditd.pid is not owned by any package avahi-0.6.31-4.1.x86_64 samba-client-3.6.5-50.1.x86_64 ConsoleKit-0.4.5-13.1.x86_64 file /run/cron.pid is not owned by any package file /run/cron.reboot is not owned by any package file /run/cups is not owned by any package dbus-1-1.5.12-5.1.x86_64 file /run/dhclient-eth0.pid is not owned by any package file /run/displaymanager.pid is not owned by any package gdm-3.4.1-5.1.x86_64 file /run/gdm.pid is not owned by any package file /run/initramfs is not owned by any package file /run/lock is not owned by any package file /run/mount is not owned by any package file /run/netconfig is not owned by any package file /run/nfs is not owned by any package file /run/nm-dhclient-eth0.conf is not owned by any package nscd-2.15-24.1.x86_64 file /run/numlock-on is not owned by any package file /run/pcscd is not owned by any package plymouth-0.8.4-14.2.x86_64 file /run/pm-utils is not owned by any package PolicyKit-0.9-37.3.x86_64 file /run/rpcbind.lock is not owned by any package file /run/rpcbind.sock is not owned by any package syslog-service-1.4.1-760.1.noarch file /run/rsyslogd.pid is not owned by any package screen-4.0.4-3.1.x86_64 file /run/sm-notify.pid is not owned by any package file /run/sshd.pid is not owned by any package file /run/systemd is not owned by any package file /run/udev is not owned by any package screen-4.0.4-3.1.x86_64 file /run/user is not owned by any package aaa_base-12.2-4.2.x86_64 vim-base-7.3.566-1.1.x86_64 file /run/xinetd.init.pid is not owned by any package and I did not find anything related in our packaging guidelines. But I would say that packages should own their (/var)/run/ content, especially the directories added to (/var)/run. Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Quoting Michal Vyskocil <mvyskocil@suse.cz>:
Hallo, and I did not find anything related in our packaging guidelines. But I would say that packages should own their (/var)/run/ content, especially the directories added to (/var)/run.
Considering that /run and /var/run live in a tmpfs, I don't see a lot of advantage in owning the files by a package (only for reasons of aesthetics). If owned, the files must be marked as %ghost anyway. Not owning them has no real side effect, as any reboot would clean them out anyway. But I agree on the fact that it needs to be defined for best practice and then adhered to (a bunch of packages are likely not even touching the files in /var/run during install) Best regards, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Le lundi 20 août 2012 à 13:14 +0200, Dominique Leuenberger a.k.a DimStar a écrit :
Quoting Michal Vyskocil <mvyskocil@suse.cz>:
Hallo, and I did not find anything related in our packaging guidelines. But I would say that packages should own their (/var)/run/ content, especially the directories added to (/var)/run.
Considering that /run and /var/run live in a tmpfs, I don't see a lot of advantage in owning the files by a package (only for reasons of aesthetics). If owned, the files must be marked as %ghost anyway. Not owning them has no real side effect, as any reboot would clean them out anyway.
Moreover, because those directories are now tmpfs, they should be created either by initscripts or using tmpfiles.d (see man tmpfiles.d, under systemd). -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, Aug 20, 2012 at 01:14:00PM +0200, Dominique Leuenberger a.k.a DimStar wrote:
Quoting Michal Vyskocil <mvyskocil@suse.cz>:
Hallo, and I did not find anything related in our packaging guidelines. But I would say that packages should own their (/var)/run/ content, especially the directories added to (/var)/run.
Considering that /run and /var/run live in a tmpfs, I don't see a lot of advantage in owning the files by a package (only for reasons of aesthetics). If owned, the files must be marked as %ghost anyway. Not owning them has no real side effect, as any reboot would clean them out anyway.
But I agree on the fact that it needs to be defined for best practice and then adhered to (a bunch of packages are likely not even touching the files in /var/run during install)
That's true - I forgot that (/var)/run is tmpfs by default, so packages should NOT own files there as it breaks rpm -V. I will add it to my TODO. Thanks Dominique Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Dominique Leuenberger a.k.a DimStar -
Frederic Crozat -
Michal Vyskocil