systemd owfs.service wrong umount path

Bug #1902448 reported by legioner
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
owfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

owfs.service use wrong path to umount: ExecStop=/usr/bin/umount %t/owfs

# ls -las /usr/bin/umount
ls: cannot access '/usr/bin/umount': No such file or directory

Correct path to umount is: /bin/umount

Main effect of this bug - unable to stop owfs service correctly:
# systemctl status owfs
● owfs.service - 1-wire filesystem FUSE mount
     Loaded: loaded (/lib/systemd/system/owfs.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2020-11-02 02:24:13 +07; 16s ago
       Docs: man:owfs(1)
   Main PID: 38938 (owfs)
      Tasks: 3 (limit: 9473)
     Memory: 1.4M
     CGroup: /system.slice/owfs.service
             └─38938 /usr/lib/owfs/owfs -c /etc/owfs.conf -c /etc/owfs.conf --allow_other /run/owfs

ноя 02 02:24:13 fatman systemd[1]: Starting 1-wire filesystem FUSE mount...
ноя 02 02:24:13 fatman systemd[1]: owfs.service: Supervising process 38938 which is not our child. We'll most likely not notice when it exits.
ноя 02 02:24:13 fatman systemd[1]: Started 1-wire filesystem FUSE mount.
# systemctl stop owfs
# systemctl status owfs
● owfs.service - 1-wire filesystem FUSE mount
     Loaded: loaded (/lib/systemd/system/owfs.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2020-11-02 02:24:33 +07; 1s ago
       Docs: man:owfs(1)
    Process: 39004 ExecStop=/usr/bin/umount /run/owfs (code=exited, status=203/EXEC)
   Main PID: 38938

ноя 02 02:24:13 fatman systemd[1]: owfs.service: Supervising process 38938 which is not our child. We'll most likely not notice when it exits.
ноя 02 02:24:13 fatman systemd[1]: Started 1-wire filesystem FUSE mount.
ноя 02 02:24:33 fatman systemd[1]: Stopping 1-wire filesystem FUSE mount...
ноя 02 02:24:33 fatman systemd[39004]: owfs.service: Failed to execute command: No such file or directory
ноя 02 02:24:33 fatman systemd[39004]: owfs.service: Failed at step EXEC spawning /usr/bin/umount: No such file or directory
ноя 02 02:24:33 fatman systemd[1]: owfs.service: Control process exited, code=exited, status=203/EXEC
ноя 02 02:24:33 fatman systemd[1]: owfs.service: Killing process 38938 (owfs) with signal SIGKILL.
ноя 02 02:24:33 fatman systemd[1]: owfs.service: Killing process 38938 (owfs) with signal SIGKILL.
ноя 02 02:24:33 fatman systemd[1]: owfs.service: Failed with result 'exit-code'.
ноя 02 02:24:33 fatman systemd[1]: Stopped 1-wire filesystem FUSE mount.

# lsb_release -rd
Description: Ubuntu 20.10
Release: 20.10
# apt-cache policy owfs
owfs:
  Installed: 3.2p3+dfsg1-6
  Candidate: 3.2p3+dfsg1-6
  Version table:
 *** 3.2p3+dfsg1-6 500
        500 http://ru.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
        500 http://ru.archive.ubuntu.com/ubuntu groovy/universe i386 Packages
        100 /var/lib/dpkg/status

Tags: patch
Revision history for this message
legioner (legioner) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "owfs.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.