FS#40961 - [systemd] upgrade to 214, /dev/log still a socket

Attached to Project: Arch Linux
Opened by Leonard de Ruijter (leonardder) - Tuesday, 24 June 2014, 13:10 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Tuesday, 24 June 2014, 22:46 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I updated two pc's running Arch Linux to Systemd 214. Although /dev/log was supposed to be a symlink to /run/systemd/journal/dev-log, it appeared to be still a socket, resulting in a program throwing errors. I had to manually remove /dev/log and reboot the system to create the symlink.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Tuesday, 24 June 2014, 22:46 GMT
Reason for closing:  Not a bug
Comment by Gerardo Exequiel Pozzi (djgera) - Tuesday, 24 June 2014, 13:14 GMT
because you did not update systemd in initramfs image, you always need to keep in sync.
Comment by Leonard de Ruijter (leonardder) - Tuesday, 24 June 2014, 13:18 GMT
Ah, that seems to fix the issue indeed.
Isn't it an option to trigger initramfs rebuild after every systemd update, just like when updating the kernel?
Comment by Dave Reisner (falconindy) - Tuesday, 24 June 2014, 13:27 GMT
No, this isn't an option. pacman does not have hooks. Generally speaking, you should rebuild your initramfs whenever a component which resides in it is upgraded. In this case, you use systemd in the initramfs, so you should rebuild your initramfs when systemd is upgraded.

Loading...