On Mo, 06.01.20 20:44, Claes H (claesatw...@gmail.com) wrote:
> On Mon, Jan 6, 2020 at 1:40 PM Lennart Poettering
> wrote:
> >
> > If possible use DynamicUser=1, i.e. have a short-lived user that only
> > exists while your service is running.
> >
> > For some usecases that doesn#t work though.
On Mon, Jan 6, 2020 at 1:40 PM Lennart Poettering
wrote:
>
> If possible use DynamicUser=1, i.e. have a short-lived user that only
> exists while your service is running.
>
> For some usecases that doesn#t work though. There's a TODO list item,
> to add AllocateUser= as new switch to create a
On So, 05.01.20 19:25, Claes H (claesatw...@gmail.com) wrote:
> Turns out the problem was not with the mount - that was working well.
> Instead it was a user problem and I did not realize the process ran as
> root and used a different home directory.
> When I added the user homeassistant in the
On Mon, 6 Jan 2020, Claes H wrote:
> Turns out the problem was not with the mount - that was working well.
> Instead it was a user problem and I did not realize the process ran as
> root and used a different home directory.
> When I added the user homeassistant in the host and added it to the
>
Turns out the problem was not with the mount - that was working well.
Instead it was a user problem and I did not realize the process ran as
root and used a different home directory.
When I added the user homeassistant in the host and added it to the
User= configuration in the service file it
