Re: Strange issue with brltty
Simon Kainz <simon@familiekainz.at> writes:
> Am 2015-08-21 um 15:16 schrieb Mario Lang:
>> Shérab <Sebastien.Hinderer@ens-lyon.org> writes:
>>
>>> Hi Mario, thanks a lot for your response.
>>>
>>> Mario Lang (2015/08/21 11:44 +0200):
>>>> Do you have START_IN_INITRAMFS enabled?
>>>
>>> I don't think so since /etc/default/brltty contains this line:
>>> START_IN_INITRAMFS=false
>>>
>>> It is worth mentionning that, on the system where the problem
>>> occurs, /var is on its own partition. Is it possible that brltty
>>> is started by systemd before /var is mounted?
>>
>> That is a possibiliy, yes. I personally didn't configure any of
>> my systems to have /var on a separate partition since a long time,
>> so I wouldn't have noticed. Thanks for reporting. I am not very
>> up-to-date on systemd, so this will need a bit of investigation. If
>> anyone knows how to set a dependency on a particular mount-oint in
>> a systemd service file, please speak up.
>
> man 5 systemd.units lists the RequiresMountsFor= option:
>
> RequiresMountsFor=
> Takes a space-separated list of absolute paths. Automatically
> adds dependencies of type Requires= and After= for all mount
> units required to access the specified path.
That sounds like is could work. Shérab, could you please try the
following:
# mkdir /etc/systemd/system/brltty.service.d
# cat <<EOF >/etc/systemd/system/brltty.service.d/mounts.conf
[Unit]
RequiresMountsFor=/var
EOF
And see if the problem re-occurs after a reboot?
--
CYa,
⡍⠁⠗⠊⠕
Reply to: