Re: [pve-devel] [PATCH pve-manager 2/2] move /run/vzdump.lock to /run/lock/vzdump.lock

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Am 24.03.25 um 14:04 schrieb Jing Luo:
> I just found that this is technically a systemd thing: at boot time,
> systemd creates the symlinks /var/run -> /run and /var/lock -> 
> /run/lock, this
> is written in /usr/lib/tmpfiles.d/var.conf and 
> /usr/lib/tmpfiles.d/legacy.conf,
> which has been true at least since Debian switched to systemd in 2015.
> 
> So these two have always been symlinks (unless the machine has not been 
> restarted
> in the past 10+ years).
> 
> [1] https://wiki.debian.org/ReleaseGoals/RunDirectory
> 

Thanks for checking, then it indeed seems fine to just do those two
specific path moves without any extra coordination or backward compat
code required.

So for moving file paths from /var/run/ to /run/ and /var/lock/ to
/run/lock, i.e. where the actual location of the file does not change
at all due the respective pairs pointing to the exact same directory,
this series is:

Acked-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

Anything where the underlying directory changes is still NAK'd if it
does not come with some backward compat handling code, FWICT this is
really just the single vzdump.lock patch though.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel