?Hi guys,
We plan to place an abstraction service over systemd-timedated and we would
like to retrieve available time zones. The timedatectl retrieves the list of
time zones by itself, but why isn't this functionality available in
systemd-timedated?
Best Regards,
Christopher Wong
Hi Lennart,
I have created a PR now.
https://github.com/systemd/systemd/pull/11856
BR,
Christopher Wong
From: Lennart Poettering
Sent: Monday, February 25, 2019 14:08
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd
it be better to use the zone1970.tab file?
Best Regards,
Christopher Wong
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
in a tz-file. Installing a symlink that point to such a tz-file will
allow us to use the systemd-timedated interface to set time zone. The
changeable tz-file (located at /etc/...) can be altered by root and a specific
service. Do you see any potential risk by doing so?
Best Regards,
Christopher
ing off the sandboxing features, i.e. add a drop-in that
> turns off ProtectSystem=, ProtectHome= and suchlike.
Just wanted to give feedback that ProtectSystem= and ProtectHome= was turned
off already, but we could no longer produce the problem we have seen. So case
closed.
BR,
Christopher Wong
__
Hi,
Is there a way to turn on a sandboxing option for all services?
We would like to on an embedded system enable as much sandboxing options as
default. Only whitelist options for services that need access to them.
Best Regards,
Christopher Wong
Thanks, seems to be working fine.
Best Regards,
Christopher Wong
From: Michael Biebl
Sent: Wednesday, September 9, 2020 22:40
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Enable sandboxing options globally
RestrictNamespaces=
SystemCallArchitectures=native
#SystemCallArchitectures=option
UMask=
#UMask=0033
I have enabled the following kernel configurations:
CONFIG_NAMESPACES=y
CONFIG_NET_NS=y
CONFIG_USER_NS=y
CONFIG_SECCOMP=y
Is there anything that I am missing?
Best Regards,
Christopher Wong
UMask for now, no need to use it at this moment.
Best regards,
Christopher Wong
From: Lennart Poettering
Sent: Saturday, December 19, 2020 11:28
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Sandboxing options
service didn't have the Type= defined. See my test service file
below:?
[Unit]
Description=MyTest
[Service]
ExecStart=/usr/local/bin/mytest
Restart=always
RestartSec=5s
CPUQuota=10%
WatchdogSec=5s
[Install]
WantedBy=multi-user.target
?
Best Regards,
Christopher Wong
CPU for a longer
time, which results in many services configured with watchdogs being fired.
Would like to disable the watchdogs during that period and resume the watchdogs
one the heavy operation is finished.
Best Regards,
Christopher Wong
___
syst
=temperature-controller.service
# /usr/lib/systemd/system/temperature-controller.service
[Unit]
Description=Temperature controller
...
After=iris-detection.service
Wants=iris-detection.service
Is it possible that After= is ignored, even if Wants= is specified?
Best Regards,
Christopher Wong
!
Merry X'mas and Happy New Year!
Christopher Wong
From: Anita Zhang
Sent: Thursday, December 23, 2021 9:21:48 AM
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] After= and Wants= doesn't seem to have an effect
I think
ure-controller.service/stop finished, result=done
Dec 22 18:03:18 axis-b8a44f278c56 systemd[1]: temperature-controller.service:
Trying to enqueue job temperature-controller.service/start/replace
Best Regards,
Christopher Wong
From: Andrei Borzenkov
Sent: Tues
> # /etc/systemd/system/iris-detection.service
> [Unit]
> Description=Iris detection
> PartOf=opticsd.service
How can you tell that it is a loop? iris-detection.service doesn't have any
After= as you stated below. Is it due to the PartOf=opticsd.service?
Best Regards,
Chri
the usage?
Best Regards
Christopher Wong
Yes, exactly.
Best Regards,
Christopher Wong
From: Lennart Poettering
Sent: Thursday, March 10, 2022 2:52:38 PM
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] PrivateNetwork=yes is memory costly
On Do, 10.03.22 11:50
everything into
the same namespace using JoinsNamespaceOf=. It seems to consume
less memory.
Best Regards,
Christopher Wong
From: Lennart Poettering
Sent: Wednesday, March 9, 2022 4:18:22 PM
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject
/systemd.service.html it is
only mentioning that when the parent process exits then the unit is started. It
doesn't mention grand-parent when type=forking and the service binary is doing
double fork().
Testing with systemd 251.3.
Best Regards,
Christopher Wong
. I shall probably
try using that instead.
Best Regards,
Christopher Wong
From: Lennart Poettering
Sent: Monday, October 31, 2022 11:43:17 AM
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Warning "Supervising pr
Hi Lennart,
Thanks for your response! We will investigate it further why this is happening
in v253 for us.
Sorry, for the confidentiality notice. Used the wrong signature.
Best regards,
Christopher Wong
Från: Lennart Poettering
Skickat: tisdag 20 juni 2023
, char *argv[]) {
int r;
setlocale(LC_ALL, "");
-log_parse_environment();
-log_open();
+log_setup();
Best regards,
Christopher Wong
Senior Engineer
christopher.w...@axis.com<mailto:firstname.lastn...@axis.com>
Tel (direct): +46 46 272 11
in file mkdir-label.c.
Do I need to do something else before starting
user@.service<mailto:user@%3cuid%3e.service> or is this a bug?
Best regards,
Christopher Wong
1001
(code=exited, status=0/SUCCESS)
Main PID: 16329 (code=exited, status=0/SUCCESS)
CPU: 48ms
/etc/fstab don’t include anything on /run/user/1001 and there is no mount unit
for run-user-1001.mount either.
Best regards,
Christopher Wong
From: Mantas Mikulėnas
Date: Tuesday, 12 D
.
Best regards,
Christopher Wong
From: Andrei Borzenkov
Date: Monday, 11 December 2023 at 19:34
To: Christopher Wong , Mantas Mikulėnas
Cc: Systemd
Subject: Re: [systemd-devel] Manual start of user@.service failed with
permission denied
On 11.12.2023 18:28, Christopher Wong wrote:
>
>. Result is that it
didn’t work.
Best regards,
Christopher Wong
From: Belanger, Martin
Date: Monday, 11 December 2023 at 17:43
To: Christopher Wong , Mantas Mikulėnas
Cc: Systemd
Subject: RE: [systemd-devel] Manual start of user@.service failed with
permission denied
Have you
oot root60 Dec 12 16:19 ..
srw-rw-rw-1 ida ssh-user 0 Dec 12 16:19 bus
drwxr-xr-x5 ida ssh-user 140 Dec 12 16:19 systemd
The ”mount” command don’t list /run/user/1001 for the successful case either.
Best regards,
Christopher Wong
From: Mantas Mikulė
to:user-runtime-dir@.service> has been exited
successfully.
Best regards,
Christopher Wong
From: Mantas Mikulėnas
Date: Wednesday, 13 December 2023 at 08:08
To: Christopher Wong
Cc: Systemd
Subject: Re: [systemd-devel] Manual start of user@.service failed with
permission denied
On Tue, Dec
,
Christopher Wong
From: Mantas Mikulėnas
Date: Wednesday, 13 December 2023 at 10:33
To: Christopher Wong
Cc: Systemd
Subject: Re: [systemd-devel] Manual start of user@.service failed with
permission denied
On Wed, Dec 13, 2023 at 10:36 AM Christopher Wong
mailto:christopher.w...@axis.com
ser-runtime-dir@.service.d> which defines
PrivateMounts=no. Now it works!
Thank you very much for your support!
Best regards,
Christopher Wong
From: systemd-devel on behalf of
Christopher Wong
Date: Wednesday, 13 December 2023 at 11:32
To: Mantas Mikulėnas
Cc: Systemd
Subject: Re: [s
, but
the result is the same. Now that I have the
“Environment=XDG_RUNTIME_DIR=/run/user/%i” I no longer need to do “systemctl
set-environment …”
Thank you for taking your time!
Best regards,
Christopher Wong
From: Mantas Mikulėnas
Date: Friday, 8 December 2023 at 21:53
To: Christopher
Hi Andrei,
As indicated in the logs no SELINUX nor APPARMOR is enabled.
Best regards,
Christopher Wong
From: systemd-devel on behalf of
Andrei Borzenkov
Date: Saturday, 9 December 2023 at 07:13
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Manual start of user
the UID 1001. Using that UID gave me the same result as the 503.
Best regards,
Christopher Wong
From: Lennart Poettering
Date: Wednesday, 6 December 2023 at 16:50
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Manual start of user@.service failed
:54 host systemd[1]: user@1001.service: Releasing resources...
Best regards,
Christopher Wong
From: Luca Boccassi
Date: Wednesday, 6 December 2023 at 17:46
To: Christopher Wong
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Manual start of user@.service failed with
permissio
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
001.
Best regards,
Christopher Wong
From: Mantas Mikulėnas
Date: Friday, 8 December 2023 at 12:11
To: Christopher Wong
Cc: Luca Boccassi , Systemd
Subject: Re: [systemd-devel] Manual start of user@.service failed with
permission denied
On Fri, Dec 8, 2023, 12:22 Christopher Wong
mailto:ch
36 matches
Mail list logo
