On 08.12.2023 23:53, Mantas Mikulėnas wrote:
...
Dec 08 17:33:29 host systemd-user-runtime-dir[36278]: Will mount
/run/user/1001 owned by 1001:118
Dec 08 17:33:29 host systemd-user-runtime-dir[36278]: Mounting tmpfs
(tmpfs) on /run/user/1001 (MS_NOSUID|MS_NODEV
On Fri, Dec 8, 2023 at 6:53 PM Christopher Wong
wrote:
> Hi Mantas,
>
>
>
> I have from your suggestion done the following:
>
>
>
> Putting the below in user@.service
>
>
>
> [Service]
>
> ...
>
> Environment=XDG_RUNTIME_DIR=/run/user/%i
>
> Environment=SYSTEMD_LOG_LEVEL=debug
>
>
>
> Putting
We have been working on a new initial filesystem called initoverlayfs.
It is a new filesystem that provides a more scalable approach to
initial filesystems as opposed to just using initrds. We are writing
this RFC to the systemd and dracut mailing lists (feel free to forward
to UAPI group also)
Hi Mantas,
I have from your suggestion done the following:
Putting the below in user@.service
[Service]
...
Environment=XDG_RUNTIME_DIR=/run/user/%i
Environment=SYSTEMD_LOG_LEVEL=debug
Putting the below in user-runtime-dir@.service
[Service]
...
Environment=SYSTEMD_LOG_LEVEL=debug
Then I
On Fri, Dec 8, 2023, 12:22 Christopher Wong
wrote:
> Hi Luca,
>
>
>
> Sorry, for late reply, below is a log with debug. This time I run with a
> user with higher UID, but the result is the same.
>
>
>
> root@host:~# systemd-analyze set-log-level debug
>
> root@host:~# systemctl set-environment
On Fr, 08.12.23 08:52, Christopher Wong (christopher.w...@axis.com) wrote:
> Hi Lennart,
>
> I know we are not using the pam_systemd. That is the reason we try
> to run the steps manually. It was possible to start the
> user@.service in systemd v253, but it fails now with v254 or
> later.
Well,
On 2023-12-07 23:03, Lennart Poettering wrote:
The 503 is a system user. So, just to try it out, I created a user,
which got the UID 1001. Using that UID gave me the same result as
the 503.
It's a bad idea to run user stuff as system user.
Lennart
Why's that?
Best regards,
Aki
Hi Lennart,
I know we are not using the pam_systemd. That is the reason we try to run the
steps manually. It was possible to start the user@.service in systemd
v253, but it fails now with v254 or later.
Best regards,
Christopher Wong
From: Lennart Poettering
Date: Thursday, 7 December 2023
Hi Luca,
Sorry, for late reply, below is a log with debug. This time I run with a user
with higher UID, but the result is the same.
root@host:~# systemd-analyze set-log-level debug
root@host:~# systemctl set-environment XDG_RUNTIME_DIR="/run/user/1001"
root@host:~# systemctl start
it's not "systemd" way but may be by blacklisting the module used by the
network card ?
and inserting it when required...
regards, lacsaP.
Le jeu. 7 déc. 2023 à 17:12, lejeczek a écrit :
> Hi guys.
>
> Perhaps not strictly _systemd_ question but community here surely is
> capable - a matter
10 matches
Mail list logo
