This commit might have introduced the issue - since /var/volatile/tmp is inside a tmpfs mount, it gets wiped on reboot, meaning /var/tmp is also cleared.

Commit - https://git.yoctoproject.org/poky/commit/meta/recipes-core/systemd/systemd/00-create-volatile.conf?h=scarthgap&id=3cc8c3520cedb66500757f843f757646da69ab30

This commit links /var/tmp to /var/volatile/tmp

Expected Behavior

/var/tmp should retain files across reboots, as per standard Linux behavior.
Using a symlink to a volatile tmpfs directory contradicts this expectation.

Impact

Any application expecting persistent temporary storage in /var/tmp will lose data after a reboot.
This behavior may break software relying on the standard /var/tmp persistence.

Should /var/tmp continue following standard Linux behavior by not being linked to /var/volatile/tmp, or is this change intentional for specific use cases? If persistence is desired, this approach seems problematic.

Would appreciate input from the maintainers on whether this is a bug or intended behavior.