On 2022-03-16 at 16:40 -0400, Dave Mielke <[email protected]> wrote: > There was a post, recently, showing how to resolve a problem by modifying > brltty's path unit. It showed how to do it by directly editing the > brtty.path unit file. While it isn't wrong to want to modify a systemd unit > file, directly editing that file is the wrong way to do it. For one thing, > the next update of that file, perhaps by upgrading the package, will lose > the change. So what's the right way?
> What you should do is create a unit override file. You do this by first > creating the unit's override directory. It has the same name as the unit > file, but with .d appended to it. For example, the override directory for > brltty.path is brltty.path.d/. Within this directory, you an have as many > override files as you wish - just make sure that you give their names the > .conf extension. The easy way to do all this is $ systemctl edit <unit-file-name> e.g. $ systemctl edit brltty.path -- Aura _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
