[systemd-devel] user unit with delayed users homes mount - ?

[Lennart Poettering]

On Fr, 14.10.22 10:59, lejeczek (peljasz at yahoo.co.uk) wrote:

> Hi guys.
>
> I'm on Centos 8 S with systemd 239.
> Users homes are mounted at later (latest?) stage off NFS so when such a user
> logs in then:
>
> -> $ systemctl --user status -l xyz.service
> Unit xyz.service could not be found.
> -> $ systemctl --user daemon-reload
> -> $ systemctl --user status -l xyz.service
> ● xyz.service - Podman container-xyz.service
>    Loaded: loaded (/apps/appownia/.config/systemd/user/xyz.service; enabled;
> vendor preset: enabled)
>    Active: inactive (dead)
>      Docs: man:podman-generate-systemd(1)
>
> Is it possible and if so then how, to make "systemd" account for such a
> "simple" case - where home dir is net mounted very late?

I don't get this scenario. You talk to the systemd --user instance,
which is the per-user instance, so $HOME of that user should be
mounted at that time. But then you issue a reload and new stuff
appears and you appear to suggest that now the user's $HOME was
mounted?

So what now? Usually, the assumption is that first the user logs in,
which is the point where $HOME must be mounted at the latest, and then
systemd --user gets started off it and the user's login session is
allowed to begin.

Lennart

--
Lennart Poettering, Berlin