FS#69339 - [uptimed] Unit file failed to locate executable

Attached to Project: Community Packages
Opened by Slash Quit (SlashQuit) - Friday, 15 January 2021, 19:42 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 16 January 2021, 00:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Unit file uptimed.service ExecStart points to wrong location.
Version: 0.4.3

The upstream unit file (in the tar.tz) ./etc/uptimed.service.in contains the line;
ExecStart=@prefix@/sbin/uptimed -f

The Arch PKGBUILD ./configure line contains the param;
--sbindir=/usr/bin

But no adjustment to the uptimed.service file is performed during installation.
This results in the binary being at "/usr/bin/uptimed", but the ExecStart line pointing to "/usr/sbin/uptimed".

Possible solutions;
1. Adjust the uptimed.service to point to /usr/bin
2. Adjust the ./configure line in the PKGBUILD to point to /usr/sbin
3. Create a symlink from /usr/sbin/uptimed to /usr/bin/uptimed


Steps to reproduce:
1. Start the uptimed daemon
systemctl start uptimed

View the journal

journalctl |grep uptimed
Jan 15 11:09:56 archgold systemd[328]: uptimed.service: Failed to locate executable /usr/sbin/uptimed: No such file or directory
Jan 15 11:09:56 archgold systemd[328]: uptimed.service: Failed at step EXEC spawning /usr/sbin/uptimed: No such file or directory
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 16 January 2021, 00:59 GMT
Reason for closing:  Not a bug
Comment by David Thurstenson (thurstylark) - Friday, 15 January 2021, 20:03 GMT
The filesystem package ships a symlink from /usr/sbin to /usr/bin/. With that in place, systemd should be able to find the binary just fine. Can you confirm this symlink still exists and is pointing at the correct location?
Comment by Slash Quit (SlashQuit) - Saturday, 16 January 2021, 00:37 GMT
Ah, then this can be closed as reported in error. Thanks for the quick response!

Another 3rd party package had created the /usr/sbin/ and so I see it as a directory with only 2 files inside.
On a system without that other package, the /usr/sbin is indeed a symlink.

Loading...