On Thu, 03.04.14 16:13, Barry Scott (barry.sc...@onelan.co.uk) wrote:
More of my porting from F16 to F20.
I have the following in /etc/udev/rules.d
ACTION==add, SUBSYSTEM==block, SUBSYSTEMS==usb,
RUN+=/usr/local/onelan/ntb/bin/ntb_mount_usb
ACTION==remove, SUBSYSTEM==block,
On Thu 03 Apr 2014 17:27:44 Thomas Bächler wrote:
Am 03.04.2014 17:13, schrieb Barry Scott:
But as soon as the script exits the mount.ntfs process is killed off by
something? systemd-udevd maybe?
From man udev's section on RUN:
This can only be used for very short-running
More of my porting from F16 to F20.
I have the following in /etc/udev/rules.d
ACTION==add, SUBSYSTEM==block, SUBSYSTEMS==usb,
RUN+=/usr/local/onelan/ntb/bin/ntb_mount_usb
ACTION==remove, SUBSYSTEM==block, SUBSYSTEMS==usb,
RUN+=/usr/local/onelan/ntb/bin/ntb_mount_usb
This run the ntb_mount_usb
Am 03.04.2014 17:13, schrieb Barry Scott:
But as soon as the script exits the mount.ntfs process is killed off by
something? systemd-udevd maybe?
From man udev's section on RUN:
This can only be used for very short-running foreground
tasks. Running an event process for a long period
2014-04-03 17:13 GMT+02:00 Barry Scott barry.sc...@onelan.co.uk:
More of my porting from F16 to F20.
I have the following in /etc/udev/rules.d
ACTION==add, SUBSYSTEM==block, SUBSYSTEMS==usb,
RUN+=/usr/local/onelan/ntb/bin/ntb_mount_usb
ACTION==remove, SUBSYSTEM==block, SUBSYSTEMS==usb,
2014-04-03 17:27 GMT+02:00 Thomas Bächler tho...@archlinux.org:
Am 03.04.2014 17:13, schrieb Barry Scott:
But as soon as the script exits the mount.ntfs process is killed off by
something? systemd-udevd maybe?
From man udev's section on RUN:
This can only be used for very
2014-04-03 17:13 GMT+02:00 Barry Scott barry.sc...@onelan.co.uk:
How should I be doing this?
As I don't know if your script is meant to mount arbitrary removable
drives, if you just want to mount a specific device, the simplest
solution is to just add it to /etc/fstab.
Use somehting like UUID or
