Hi all, as some of you might have noticed with recent systemd, you can see a warning at startup stating : var-lock.mount: Directory /var/lock to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) var-run.mount: Directory /var/run to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) This warning is caused by some packages installing either files or directories in /var/run (or /var/lock) which are later bind-mount to /run (/run/lock) which is a tmpfs, hiding files beneath. Robert Milasan has fixed some packages like dbus, avahi and unscd (moving them also from /var/run to /run) but feel free to help, making sure packages never create files nor directories in /var/run (and at the same time, migrate them to use /run instead) nor /var/lock. If a directory or a file needs to be created with specific permissions, package a tmpfiles.d file instead (see manpage). And if you want a file / directory to be "owned" by a package but at the same time, it will be stored on a tmpfs mount point (/var/run , /var/lock, /run), use %ghost so rpm will not write the file on disk. Thanks for your help. -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org