Arch Linux

indrajitr

Member

Registered: 2015-05-15

Posts: 1

Hooks (part 2), aka systemd pacman hooks

Hello packagers,

Wondering what is the plan for next round of hooks, particularly the ones involving systemd-tmpfiles to be put in place.

While Hooks (part 1) didn't involve system related hooks, we do have at least one package (apcupsd) in the repo that assumes presence of such hook in the system.

As a result, the first run after installation

systemctl start apcupsd

results in log that looks like this:

Jul 13 16:31:56 archlinux-test apcupsd[9149]: Cannot create /run/apcupsd/LCK..hiddev[0-9] serial port lock file: ERR=No such file or directory
Jul 13 16:31:56 archlinux-test apcupsd[9149]: apcupsd FATAL ERROR in apcupsd.c at line 221
Jul 13 16:31:56 archlinux-test apcupsd[9149]: Unable to create UPS lock file.
Jul 13 16:31:56 archlinux-test apcupsd[9149]:   If apcupsd or apctest is already running,
Jul 13 16:31:56 archlinux-test apcupsd[9149]:   please stop it and run this program again.
Jul 13 16:31:56 archlinux-test apcupsd[9149]: apcupsd FATAL ERROR in apcupsd.c at line 221
                                              Unable to create UPS lock file.
                                                If apcupsd or apctest is already running,
                                                please stop it and run this program again.
Jul 13 16:31:56 archlinux-test apcupsd[9149]: apcupsd error shutdown completed
Jul 13 16:31:56 archlinux-test systemd[1]: apcupsd.service: Main process exited, code=exited, status=1/FAILURE

Of course, this will correct itself after system restart, but that's probably not ideal. This can also be corrected by rolling back the specific commit(s).

But we might as well take the opportunity to apply some of the systemd hooks that have been discussed (at least the easy ones).

Thoughts?

- Indrajit