Bug#762041: systemd: upgrading systemd results in /run/user/<uid> being emptied

[Michael Biebl]

Am 21.09.2014 um 20:51 schrieb Ansgar Burchardt:
> I suspect logind just mounts the tmpfs when it unserializes the session
> state on restart. Probably the call to user_start in manager_startup
> does so (which then calls user_mkdir_runtime_path).

Thanks for the input Ansgar.
I guess we should just add an additional check to
user_mkdir_runtime_path(), to not mount an tmpfs if the runtime
directory already exists and is non-empty.

Afaics this can only happen on upgrades, and in this case we already
have a separate tmpfs for /run/user (which will persist until the next
reboot).
So it should be safe to not use a separate tmpfs mount in this case.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140921/b1d9426b/attachment-0002.sig>