Yeah, brltty.path did it.
- Original Message -
From: Dave Mielke
To: "Informal discussion between users and developers of BRLTTY."
Date: Fri, 13 Oct 2023 05:27:23 -0400
Subject: Re: [BRLTTY] Restarting brltty via .path service
> [quoted lines by Rob Hudson on 2023/10/12 a
[quoted lines by Rob Hudson on 2023/10/12 at 20:58 -0500]
>/usr/lib/systemd/system/brltty.path
>/usr/lib/systemd/system/brltty@.path
But you said you used the unit name brltty@path.service. That name doesn't make
sense. Check README.Systemd for the details.
Are you using /etc/brltty.conf? If
/usr/lib/systemd/system/brltty.path
/usr/lib/systemd/system/brltty@.path
- Original Message -
From: Dave Mielke
To: "Informal discussion between users and developers of BRLTTY."
Date: Thu, 12 Oct 2023 18:29:47 -0400
Subject: Re: [BRLTTY] Restarting brltty via .path service
[quoted lines by Rob Hudson on 2023/10/12 at 15:14 -0500]
>I have a display connected via USB to serial, so brltty is invoked with
>brltty@path.service.
How are you coming up with that name? Why the @path?
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke
Did you try
systemctl stop brltty.service
systemctl start brltty.service
Not saying that will fix the problem, but maybe it will give you some
information.
On 10/12/23 16:14, Rob Hudson wrote:
I have a display connected via USB to serial, so brltty is invoked with
brltty@path.service. But
