You are not logged in.
I just upgraded to systemd-218-2, and was told
warning: directory ownership differs on /var/log/journal/remote/
filesystem: 0:996 package: 0:0
I can see that this directory is owned by root:systemd-journal-remote. Should I manually change permissions?
Last edited by Salkay (2015-02-17 13:11:55)
Offline
I got the same warning, except that on my system the current UID:GID is 0:998 (which is also root:systemd-journal-remote). I couldn't find anything in the ABS tree which sets this ownership. In fact, I couldn't even find any mention of the users systemd-journal-remote and systemd-journal-upload at all in the ABS tree.
Those users were added some time ago, but apparently aren't needed anymore. Would it be safe to delete them?
Offline
Those users were added some time ago, but apparently aren't needed anymore. Would it be safe to delete them?
Those users are created dynamically by systemd-sysusers. There's no point in deleting them as they will be recreated on boot.
Offline
By the same token, there's no point in changing the ownership of the directory because of that warning -- tmpfiles.d changes the ownership of the directory every boot anyway.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thank you for the answers. So if I read it correctly, we should essentially ignore the warnings.
Offline
Those users were added some time ago, but apparently aren't needed anymore. Would it be safe to delete them?
Weren't there some pacnew files created on upgrade?
Offline
Weren't there some pacnew files created on upgrade?
Not for me.
Offline
Ah, OK, filesystem 2015.02-1 is still in testing:
[2015-02-16 21:25] [ALPM] warning: /etc/group installed as /etc/group.pacnew
[2015-02-16 21:25] [ALPM] warning: /etc/gshadow installed as /etc/gshadow.pacnew
Offline