On Mon, 7 Dec 2015, Dave Mielke wrote:
but it still doesn't start up correctly, but I
think that that is basically a known issue in that the udev file
isn't intended to work unmodified with systemd. Ie, the systemd
documentation indicates that the Run directive is intended for a
short-running program, rather than a daemon, and it will kill the
program if it does not exit shortly after being started.
The latest brltty service unit for systemd assumes that configure has
autodetected the systemd development package. If configure isn't autodetecting
systemd's development package then the older brltty service unilt needs to be
used. I'll add it back to the repository and write a bit about this in
README.Systemd.
Okay, but that isn't what I was referring to, fwiw.
From Autostart/Udev/udev.rules:
LABEL="brltty_add"
SYMLINK+="brltty/$env{BRLTTY_BRAILLE_DRIVER}-$env{BRLTTY_BRAILLE_DEVICE}"
RUN+="/bin/brltty -E -P$env{BRLTTY_PID_FILE}"
GOTO="brltty_end"
From the udev manpage on my system:
RUN{type}
Add a program to the list of programs to be executed after processing all the
rules for a specific event, depending on "type":
...
This can only be used for very short-running foreground tasks.
Running an event process for a long period of time may block all further events
for this or a dependent device.
Starting daemons or other long-running processes is not appropriate
for udev; the forked processes, detached or not, will be unconditionally killed
after the event handling has
finished.
Anyway, this has been discussed on the list before; I've been trying to
modify my udev file to start brltty via systemd but haven't succeeded in
actually getting it to start so far, although it will start if I manually
start it via systemctl or probably if I enable it to start at boot-up.
-Mike
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@mielke.cc
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
