Re: [systemd-devel] Discrepancy in using dhclient b/w ubuntu 20.04 and ubuntu 16.04

Am 08.06.21 um 15:44 schrieb Aravindhan Krishnan: With all due respect, it would be very helpful if you can be a little bit less snarky. With all due respect, it would be very helpful not use reply-all and not convert each and every response to HTML i don't get the bash-nonsense for a

Re: [systemd-devel] Discrepancy in using dhclient b/w ubuntu 20.04 and ubuntu 16.04

stemd-unit? it's impressive how many layers and helpers one can wrap around simple tasks but to gain what except troubles? keep it simple! On Mon, 7 Jun 2021 at 21:53, Reindl Harald <mailto:h.rei...@thelounge.net>> wrote: Am 07.06.21 um 17:57 schrieb Aravindhan Krishnan:

Re: [systemd-devel] Discrepancy in using dhclient b/w ubuntu 20.04 and ubuntu 16.04

Am 07.06.21 um 17:57 schrieb Aravindhan Krishnan: Adding Raghav. And sorry the subject should have stated: Discrepancy in using dhclient b/w ubuntu 20.04 and ubuntu 16.04 and why didn't you fix it in your own reply? to your problem: you have a wild mix of docker, systemd-units and

Re: [systemd-devel] Adding USB ID to hwdb/usb.ids

Am 02.06.21 um 16:39 schrieb Greg KH: On Wed, Jun 02, 2021 at 03:48:41PM +0200, Reindl Harald wrote: Am 02.06.21 um 07:04 schrieb Greg KH: On Tue, Jun 01, 2021 at 09:38:37PM +0200, Michael Biebl wrote: Am Di., 1. Juni 2021 um 20:44 Uhr schrieb Greg KH : Works for me! Make sure you

Re: [systemd-devel] Adding USB ID to hwdb/usb.ids

Am 02.06.21 um 07:04 schrieb Greg KH: On Tue, Jun 01, 2021 at 09:38:37PM +0200, Michael Biebl wrote: Am Di., 1. Juni 2021 um 20:44 Uhr schrieb Greg KH : Works for me! Make sure you are not trying to connect to 'https'. No https? Why? Because why would serving up text files about this

Re: [systemd-devel] What causes "systemd-journald[3256]: Missed 127 kernel messages"

Am 01.06.21 um 12:42 schrieb Ulrich Windl: Jun 01 12:33:10 h18 systemd-journald[3256]: Missed 134 kernel messages Jun 01 12:33:10 h18 systemd-journald[3256]: Missed 139 kernel messages Jun 01 12:33:10 h18 systemd-journald[3256]: Missed 413 kernel messages Jun 01 12:33:10 h18

Re: [systemd-devel] syscall-filters killing CGI after update to Fedora 33

it's the blacklisting of @resources which was as far as i remember a back-and-forth years ago between dist-upgrades looks like systemd-246.13-1.fc33.x86_64 is covering too much here in case of blacklisting Am 19.04.21 um 18:24 schrieb Reindl Harald: after a long time using

[systemd-devel] syscvall-filters killing CGI after update to Fedora 33

after a long time using this SystemCallFilter perl-cgi with Fedora 33 get killed - anyone an idea what changed that's obviously covered by the second line SystemCallFilter=@system-service @network-io @privileged SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete

Re: [systemd-devel] is such a 'failed' state?

Am 28.03.21 um 21:19 schrieb lejeczek: I have a service (which for some reason, I suspect SELinux, does not start at boot) which reports as: -> $ systemctl status -l lsyncd | cat ● lsyncd.service - Live Syncing (Mirror) Daemon    Loaded: loaded (/usr/lib/systemd/system/lsyncd.service;

Re: [systemd-devel] Only start a tomcat server when you are sure that time-sync.target is online

Am 25.03.21 um 15:11 schrieb Jan Hugo Prins: > Does systemd give me a different way to check if the time is in sync? > Is there a way to create this dependency without implying a restart when > ntpd restarts? https://unix.stackexchange.com/questions/388586/systemd-requires-vs-wants

Re: [systemd-devel] Only start a tomcat server when you are sure that time-sync.target is online

Am 25.03.21 um 14:41 schrieb Jan Hugo Prins: Our current configuration looks roughly like this: [Unit] Description=Apache Tomcat Web Application Container After=syslog.target time-sync.target Requires=time-sync.target [Service] Type=simple ExecStart=Startscripts ExecStop=Stopscript

Re: [systemd-devel] Q; syslog.socket dependency

Am 11.03.21 um 12:17 schrieb Ulrich Windl: Hi! I have a unit that uses logger, and I want to run it after syslog is available. So I added syslog.socket as dependency, but it fails: Mar 11 12:11:02 jeos1 systemd[1]: syslog.socket: Socket service syslog.service not loaded, refusing. Mar 11

Re: [systemd-devel] Activate netdev only on demand (e.g. for wireguard connection)

Am 11.03.21 um 06:36 schrieb Amish: Hello So I have a wireguard setup which I use to connect to my server. But I do not connect to it daily, just once a in a while. I have setup wg0.netdev file and wg0.network file and all is working fine. But how do I set it up such that interface wg0

Re: [systemd-devel] Antw: [EXT] D-bus connection Unknown error

Am 03.03.21 um 07:59 schrieb Ulrich Windl: Shiju Email <994...@gmail.com> schrieb am 02.03.2021 um 22:27 in Nachricht : Hi, I am getting an error when any systemctl commands are issued. Failed to get D-bus connection: Unknown error -1 I have no idea, but I think "unknown error" is bad

Re: [systemd-devel] Q: Roles for a one-shot service

Am 25.02.21 um 08:12 schrieb Ulrich Windl: Hi! I wonder: I'm thinking of a monitoring-type of one-shot service that should be run periodically to update some external status display with runtime data. In addition to that periodic activations, I'd like to run the service also during boot

Re: [systemd-devel] Unprivileged user can kill root-owned processes by changing PID file and stopping service

Am 19.02.21 um 21:05 schrieb Frank Thommen: Lennart Poettering hat am 19.02.2021 15:44 geschrieben: On Fr, 19.02.21 15:12, Frank Thommen (systemd-de...@lists.drosera.ch) wrote: Dear all, I am experiencing the issue, that an unprivileged user can kill root-owned processes by

Re: [systemd-devel] Looking for known memory leaks triggered by stress testing add/remove/up/down interfaces

Am 19.02.21 um 11:28 schrieb Robert P. J. Day: I *may* have found the problem ... as one can read here: https://access.redhat.com/solutions/3840481 "CVE-2019-3815 systemd: memory leak in journald-server.c introduced by fix for CVE-2018-16864" So as I interpret that, a memory leak

Re: [systemd-devel] Antw: [EXT] Re: Looking for known memory leaks triggered by stress testing add/remove/up/down interfaces

Am 19.02.21 um 08:44 schrieb Ulrich Windl: Lennart Poettering schrieb am 18.02.2021 um 19:30 in Nachricht : ... entry instead of asking for new memory again. This allocation cache is a bit quicker then going to malloc() all the time, but means if you just watch the heap you'll assume

Re: [systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 08.02.21 um 23:42 schrieb Mike Gilbert: On Mon, Feb 8, 2021 at 2:31 PM Reindl Harald wrote: I think removing this symlink would prevent /sys/fs/fuse/connections from being mounted and the fuse module from being loaded unconditionally on boot no https://bugzilla.redhat.com/show_bug.cgi

Re: [systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 09.02.21 um 17:13 schrieb Mike Gilbert: On Tue, Feb 9, 2021 at 6:17 AM Reindl Harald wrote: Am 08.02.21 um 23:42 schrieb Mike Gilbert: On Mon, Feb 8, 2021 at 2:31 PM Reindl Harald wrote: I think removing this symlink would prevent /sys/fs/fuse/connections from being mounted

Re: [systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 09.02.21 um 23:18 schrieb Mike Gilbert: On Tue, Feb 9, 2021 at 11:47 AM Reindl Harald wrote: Am 09.02.21 um 17:13 schrieb Mike Gilbert: On Tue, Feb 9, 2021 at 6:17 AM Reindl Harald wrote: Am 08.02.21 um 23:42 schrieb Mike Gilbert: On Mon, Feb 8, 2021 at 2:31 PM Reindl Harald

Re: [systemd-devel] Antw: [EXT] Re: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 09.02.21 um 08:54 schrieb Ulrich Windl: Reindl Harald schrieb am 08.02.2021 um 19:01 in Nachricht : Am 08.02.21 um 18:27 schrieb Lennart Poettering: On So, 07.02.21 22:43, Reindl Harald (h.rei...@thelounge.net) wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1909805 In response

Re: [systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 08.02.21 um 20:23 schrieb Mike Gilbert: On Mon, Feb 8, 2021 at 1:01 PM Reindl Harald wrote: Am 08.02.21 um 18:27 schrieb Lennart Poettering: On So, 07.02.21 22:43, Reindl Harald (h.rei...@thelounge.net) wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1909805 In response

Re: [systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 08.02.21 um 18:27 schrieb Lennart Poettering: Masking is a last resort thing, you really want to use that only after having investigated everything. You use it here anyway to mask out a really low-level system thing, hence you might get warnings about this. You can of course mask

Re: [systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

Am 08.02.21 um 18:27 schrieb Lennart Poettering: On So, 07.02.21 22:43, Reindl Harald (h.rei...@thelounge.net) wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1909805 In response to your actual issue, ignoring all the nasty wording: Masking is a last resort thing, you really want

Re: [systemd-devel] Antw: [EXT] Re: Still confused with socket activation

Am 08.02.21 um 14:52 schrieb Uoti Urpala: On Mon, 2021-02-08 at 11:27 +0100, Reindl Harald wrote: this is *not* what systemd-sockets are for they are for service is started at the first connect This is wrong. Socket units are useful completely independently of whether the unit is started

Re: [systemd-devel] Antw: [EXT] Re: Still confused with socket activation

Am 08.02.21 um 10:10 schrieb Ulrich Windl: Andrei Borzenkov schrieb am 06.02.2021 um 09:14 in Nachricht <09aa6a69-ee37-ffea-c4fd-e4c5d3327...@gmail.com>: 04.02.2021 10:47, Ulrich Windl пишет: ... I had provided the full units yesterday. Basically I don't know what to do: I just want

[systemd-devel] sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe@fuse.service is masked

https://bugzilla.redhat.com/show_bug.cgi?id=1909805 what is this new nonsense given that only one out of 50 installs here have a business for fuse at all and there is no reason to load/touch any fuse related stuff at boot ___ systemd-devel mailing

Re: [systemd-devel] Still confused with socket activation

Am 04.02.21 um 12:46 schrieb Benjamin Berg: On Wed, 2021-02-03 at 16:43 +0100, Reindl Harald wrote: seriously - explain what you expect to happen in case of Requires=a.service Before=a.service except some warning that it's nonsense So, one way I used it is as ExecStartPost= equivalent

Re: [systemd-devel] Still confused with socket activation

Am 03.02.21 um 10:43 schrieb Benjamin Berg: On Wed, 2021-02-03 at 08:00 +0100, Reindl Harald wrote: Am 02.02.21 um 22:25 schrieb Benjamin Berg: On Tue, 2021-02-02 at 22:50 +0300, Andrei Borzenkov wrote: 02.02.2021 17:59, Lennart Poettering пишет: Note that Requires= in almost all cases

Re: [systemd-devel] Still confused with socket activation

Am 02.02.21 um 22:25 schrieb Benjamin Berg: On Tue, 2021-02-02 at 22:50 +0300, Andrei Borzenkov wrote: 02.02.2021 17:59, Lennart Poettering пишет: Note that Requires= in almost all cases should be combined with an order dep of After= onto the same unit. Years ago I asked for example when

Re: [systemd-devel] service runs - but it's not really there

Am 29.01.21 um 16:27 schrieb lejeczek: I think I found it, in my opinion a very cheeky bastard - syncthing - who does this: [Install] WantedBy=default.target which results in: -> $ llr /etc/systemd/user/default.target.wants/ total 0 lrwxrwxrwx. 1 root root 39 Jan 26 10:39

Re: [systemd-devel] service runs - but it's not really there

Am 29.01.21 um 13:55 schrieb lejeczek: ● user@0.service - User Manager for UID 0     Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled)     Active: active (running) since Thu 2021-01-28 17:13:01 GMT; 2h 34min ago   Main PID: 854314 (systemd)     Status:

Re: [systemd-devel] What exactly is multi-seat? -- questions about logind

Am 26.01.21 um 10:43 schrieb Kian Kasad: Hi all, After reading the documentation on logind and multi-seat (specifically sd-login(3) and "Multi-Seat on Linux"), I still have some questions. First of all, what exactly is multi-seat? Google "systemd multiseat" links to

Re: [systemd-devel] Why systemd-nspawn is slower than docker, podman and qemu?! how to Improve nspawn performance?

there is a difference between theoretical academic benchmarks and real world load - if your workload isn't affected it's pointless Am 25.01.21 um 14:00 schrieb Badr Elmers: Tomasz Torcz In fact I m just comparing containers, I have no need yet for context switch, but I hope to

Re: [systemd-devel] Antw: Re: Antw: [EXT] emergency shutdown, don't wait for timeouts

Am 07.01.21 um 09:15 schrieb Ulrich Windl: Chris Murphy schrieb am 06.01.2021 um 03:02 in Nachricht : On Mon, Jan 4, 2021 at 12:43 PM Phillip Susi wrote: This is too long for a desktop or laptop use case. It should be around 15‑20 seconds. It's completely reasonable for users to reach for

Re: [systemd-devel] Is LTO worth it?

Am 11.01.21 um 18:10 schrieb Michael Biebl: Am Mo., 11. Jan. 2021 um 18:07 Uhr schrieb Reindl Harald : it don't make sense using different flags in CI and production builds, especially LTO which often points out otherwise unvisible bugs Such as? I don't remember any bug report which

Re: [systemd-devel] Antw: [EXT] emergency shutdown, don't wait for timeouts

Am 04.01.21 um 20:41 schrieb Phillip Susi: Reindl Harald writes: i have seen "user manager" instances hanging for way too long and way more than 3 minutes over the last 10 years The default timeout is 3 minutes iirc, so at that point it should be forcibly killed. i have

Re: [systemd-devel] Is LTO worth it?

Am 11.01.21 um 16:05 schrieb Michael Biebl: Am Mo., 11. Jan. 2021 um 15:42 Uhr schrieb Reindl Harald : it shouldn't if properly used - means param with cpu-cores, just -flto alone is terrible slow -flto=%(nproc) %{__make} %{?_smp_mflags} The package uses meson's -Db_lto=true export

Re: [systemd-devel] Antw: Re: Antw: [EXT] emergency shutdown, don't wait for timeouts

Am 04.01.21 um 16:04 schrieb Ulrich Windl: Reindl Harald schrieb am 04.01.2021 um 14:53 in Nachricht <49b8413f-3131-658f-e21a-a1ee448a0...@thelounge.net>: Am 04.01.21 um 13:42 schrieb Ulrich Windl: Germano Massullo schrieb am 27.12.2020 um 14:26 in Nachricht : Good day, I re

Re: [systemd-devel] Is LTO worth it?

Am 11.01.21 um 18:05 schrieb Michael Biebl: Am Mo., 11. Jan. 2021 um 16:39 Uhr schrieb Lennart Poettering : https://fedoraproject.org/wiki/LTOByDefault Interestingly, that wiki page says, that LTO should produce smaller binaries, which clearly isn't the case here. I wonder whether the wiki

Re: [systemd-devel] Is LTO worth it?

Am 11.01.21 um 15:34 schrieb Michael Biebl: we've been using LTO in the Debian build for as long as I can remember, but I begin to question whether that is a good idea. On Debian sid (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1), an LTO build almost takes

Re: [systemd-devel] Antw: [EXT] emergency shutdown, don't wait for timeouts

Am 04.01.21 um 20:06 schrieb Phillip Susi: Reindl Harald writes: topic missed - it makes no difference if it can hold the power 3 minutes, 3 hours or even 3 days at the point where it decides "i need to shutdown everything because the battery goes empty" It is that point t

Re: [systemd-devel] Antw: [EXT] emergency shutdown, don't wait for timeouts

Am 04.01.21 um 13:42 schrieb Ulrich Windl: Germano Massullo schrieb am 27.12.2020 um 14:26 in Nachricht : Good day, I recently joined apcupsd (APC UPS Power Control Daemon) package maintainers on Fedora/CentOS/RHEL. After a power failure, apcupsd shuts down the system with a command almost

Re: [systemd-devel] SystemD dependency problem

Am 22.12.20 um 14:17 schrieb Mantas Mikulėnas: As a special case, when a target has Wants= for some unit, it will automatically add an After= as well. (So from your unit's point of view, you have [Install] WantedBy=network-online.target, so you can imagine that you automatically have a

Re: [systemd-devel] emergency shutdown, don't wait for timeouts

Am 27.12.20 um 15:40 schrieb Andrei Borzenkov: 27.12.2020 17:00, Reindl Harald пишет: Am 27.12.20 um 14:43 schrieb Andrei Borzenkov: 27.12.2020 16:26, Germano Massullo пишет: Good day, I recently joined apcupsd (APC UPS Power Control Daemon) package maintainers on Fedora/CentOS/RHEL

Re: [systemd-devel] require a system service unit to start a user service as a dependency

Am 24.12.20 um 11:38 schrieb John: On Thu, Dec 24, 2020 at 3:29 AM Andrei Borzenkov wrote: On Thu, Dec 24, 2020 at 5:48 AM John wrote: I need to have the following start /usr/lib/systemd/user/pulseaudio.service so it can make use of pulseaudio. Using a After= or Wants= does not work.

Re: [systemd-devel] emergency shutdown, don't wait for timeouts

Am 27.12.20 um 14:43 schrieb Andrei Borzenkov: 27.12.2020 16:26, Germano Massullo пишет: Good day, I recently joined apcupsd (APC UPS Power Control Daemon) package maintainers on Fedora/CentOS/RHEL. After a power failure, apcupsd shuts down the system with a command almost identical to

Re: [systemd-devel] SystemD dependency problem

Am 22.12.20 um 12:17 schrieb Ronald Wimmer: On a server running OL 7.9 with SystemD 219 we have a custom SystemD service we have something like [Unit] Requires=network.target docker.service [Service] Restart=always RestartSec=10 TimeoutSec=300 WorkingDirectory=/data/someapplication

Re: [systemd-devel] service kills application differently on shutdown vs on stop

Am 14.12.20 um 17:22 schrieb John: Thank you for the reply, Colin. I found that to be the case[1]. I think everything is working as expected now. I still have quirks with the kodi-x11.service since it has to call xinit as well as the kodi binary but I do not know of a cleaner way to do it

Re: [systemd-devel] Help with Systemd + Apache 2.4 - CentOS 7

Am 23.11.20 um 02:32 schrieb Lucas Possamai: Hi, I have Apache 2.4.6-93 running on a CentOS 7.8.2003 that is not starting using Systemd. If I do: /systemctl start httpd/, I get the following error: Nov 22 20:14:11 localhost systemd[1]: Failed to start The Apache HTTP Server.

Re: [systemd-devel] Help with Systemd + Apache 2.4 - CentOS 7

Am 23.11.20 um 11:22 schrieb Michael Biebl: Am Mo., 23. Nov. 2020 um 02:33 Uhr schrieb Lucas Possamai : Hi, I have Apache 2.4.6-93 running on a CentOS 7.8.2003 that is not starting using Systemd. If I do: systemctl start httpd, I get the following error: Nov 22 20:14:11 localhost

Re: [systemd-devel] Journald retaining logs for only 10 days

Am 14.11.20 um 21:29 schrieb Vito Caputo: [Journal] SystemMaxUse=300M One thing to consider is journald allocates space per-file in 8MiB increments. On my laptop for example, there are 27 user journals, 8MiB each, where the last object offset is around 2MiB. This alone burns ~162MiB in

Re: [systemd-devel] Workaround for system upgrade bug suggestions

Am 03.11.20 um 14:56 schrieb Barry: On 3 Nov 2020, at 12:39, Colin Guthrie wrote: Barry wrote on 02/11/2020 22:20: What is the work around until the bug is fixed? I'd imagine you could just disable lingering for the users in question before running the dnf upgrade command? Not ideal but

Re: [systemd-devel] systemctl reboot/halt with non-privilege user

Am 28.10.20 um 12:40 schrieb An Liu: Hi, folks, I used to type systemctl reboot with non-privileged users, and to my surprise, the system goes down for the reboot. I've tested in both debian and centos 7, they act the same, however, systemctl halt will prompt you to enter administrator

Re: [systemd-devel] Suppressing spam error messages in the system journal

Am 22.10.20 um 21:45 schrieb fox: While it may be true that "frontends" might provide some filtering (rsyslog, plenty of options, journalctl much less) in COCKPIT that filtering is easy, effective and intuitive to perform well, us greybeards don't need handholding for configure machines

Re: [systemd-devel] Suppressing spam error messages in the system journal

Am 22.10.20 um 16:55 schrieb Dave Howorth: On Thu, 22 Oct 2020 15:27:58 +0200 Reindl Harald wrote: Am 22.10.20 um 12:59 schrieb Lennart Poettering: On Do, 22.10.20 11:11, David C. Partridge (david.partri...@perdrix.co.uk) wrote: 1) Is there any way in journald.conf to perform

Re: [systemd-devel] Suppressing spam error messages in the system journal

Am 22.10.20 um 12:59 schrieb Lennart Poettering: On Do, 22.10.20 11:11, David C. Partridge (david.partri...@perdrix.co.uk) wrote: 1) Is there any way in journald.conf to perform a message suppression similar to the one I used for syslog? If not should there be one? No. Does

Re: [systemd-devel] How to reply to the list

Am 01.10.20 um 09:31 schrieb Lennart Poettering: > On Mi, 30.09.20 11:08, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Am 30.09.20 um 09:35 schrieb Ulrich Windl: >>>>>> Dave Howorth schrieb am 28.09.2020 um 16:34 in >>> Nachricht <2020092815342

Re: [systemd-devel] Antw: Re: Antw: [EXT] Re: Memory in systemctl status

Am 30.09.20 um 11:04 schrieb Ulrich Windl: >>>> Reindl Harald schrieb am 30.09.2020 um 10:56 in > Nachricht : > >> >> Am 30.09.20 um 09:06 schrieb Ulrich Windl: >>>> my webserver is killed because it served at monday, tuesday, thursday &

Re: [systemd-devel] How to reply to the list

Am 30.09.20 um 09:35 schrieb Ulrich Windl: >>>> Dave Howorth schrieb am 28.09.2020 um 16:34 in > Nachricht <20200928153422.6bf6e...@acer-suse.lan>: >> On Mon, 28 Sep 2020 14:10:38 +0200 >> Reindl Harald wrote: >>> can you stop "reply‑all"

Re: [systemd-devel] Antw: [EXT] Re: Memory in systemctl status

Am 30.09.20 um 09:11 schrieb Ulrich Windl: >>>> Reindl Harald schrieb am 28.09.2020 um 11:37 in >> httpd don't use 8.7 GB RAM - period > > Are you really sure about that? 1000% sure even if one makes the mistake and multiply the shared opcache of 400 MB with the c

Re: [systemd-devel] Antw: [EXT] Re: Memory in systemctl status

Am 30.09.20 um 09:06 schrieb Ulrich Windl: >> my webserver is killed because it served at monday, tuesday, thursday >> and friday 4 different files with 2 GB? > > cgroups is for limiting resources, not for killing processes AFAIK [Service] MemoryMax=4G would call OOM killer

Re: [systemd-devel] Memory in systemctl status

Am 28.09.20 um 19:32 schrieb Dave Howorth: >> the far slower copy from the list-server is silently purged by >> intention to avoid receive ever ymessage twice on mailing lists where >> people can't handle a MUA > > Well then, it's not Benjamin breaking the threading, it's you :P > You need to

Re: [systemd-devel] Memory in systemctl status

Am 28.09.20 um 18:33 schrieb Lennart Poettering: > On Mo, 28.09.20 14:22, Reindl Harald (h.rei...@thelounge.net) wrote: > >> honestly: do you realize that i know very well how the memory management >> of Linux works and that it's pretty fine but not part of the topic at all

Re: [systemd-devel] Memory in systemctl status

Am 28.09.20 um 16:34 schrieb Dave Howorth: > On Mon, 28 Sep 2020 14:10:38 +0200 > Reindl Harald wrote: >> can you stop "reply-all" and breaking threads when respond to lists? > > I can't answer for the reply-all, that would annoy me as well. > But the thread

Re: [systemd-devel] Memory in systemctl status

honestly: do you realize that i know very well how the memory management of Linux works and that it's pretty fine but not part of the topic at all? Am 28.09.20 um 14:08 schrieb Greg KH: > How do you know this? And why wouldn't they be "charged" to the task > that caused the cache to fill up?

Re: [systemd-devel] Memory in systemctl status

can you stop "reply-all" and breaking threads when respond to lists? Am 28.09.20 um 13:55 schrieb Benjamin Berg: > On Mon, 2020-09-28 at 11:37 +0200, Reindl Harald wrote: >> >> Am 28.09.20 um 11:19 schrieb Benjamin Berg: >>>> if i would set "MemoryMax&quo

Re: [systemd-devel] Memory in systemctl status

Am 28.09.20 um 11:19 schrieb Benjamin Berg: >> if i would set "MemoryMax" to 4G "Memory: 8.6G" would kill it when the >> caches are accounted in that context > > No, the kernel kicks in and reclaims memory at that point. Which can > mean either swapping or just dropping caches. caches have

Re: [systemd-devel] Memory in systemctl status

Am 28.09.20 um 10:37 schrieb Tomasz Torcz: > On Mon, Sep 28, 2020 at 10:08:15AM +0200, Reindl Harald wrote: >> Am 27.09.20 um 23:39 schrieb Benjamin Berg: >>>>>> however, that value makes little to no sense and if that's the same >>>>>> value

Re: [systemd-devel] Memory in systemctl status

Am 27.09.20 um 23:39 schrieb Benjamin Berg: however, that value makes little to no sense and if that's the same value as accounted for "MemoryMax" it's plain wrong > But it does make sense. File caches are part of the working set of > memory that a process needs. Setting

Re: [systemd-devel] Memory in systemctl status

Am 27.09.20 um 14:08 schrieb Greg KH: > On Sun, Sep 27, 2020 at 01:41:33PM +0200, Reindl Harald wrote: >> Memory: 8.6G >> >> looks like there is a large part of os-caching included where i wonmder >> how that's done because a file can be read by muliple processes / &g

[systemd-devel] Memory in systemctl status

Memory: 8.6G looks like there is a large part of os-caching included where i wonmder how that's done because a file can be read by muliple processes / services and is hopfefully only once cached however, that value makes little to no sense and if that's the same value as accounted for

Re: [systemd-devel] 99-default.link which such a high number ?

Am 25.09.20 um 16:46 schrieb Francis Moreau: > I want to override /usr/lib/systemd/network/99-default.link so I need > to create a file starting with "99-" prefix. > > This doesn't seem logical to me because the numbers are supposed to > encode the priority however nothing is left to the user

Re: [systemd-devel] journald forwarding to rsyslogd. Huge (350 times) performance degradation. What am I doing wrong???

urnald.conf [Journal] Storage=volatile RateLimitInterval=1s RateLimitBurst=2 RuntimeMaxUse=100M ForwardToSyslog=no >> Max rate at which log messages are NOT dropped is 17250 msg/s for logging to >> /run/systemd/journal/syslog. And only 47 messages per second for logging to >>

Re: [systemd-devel] journald forwarding to rsyslogd. Huge (350 times) performance degradation. What am I doing wrong???

Am 20.09.20 um 12:07 schrieb Vitaly Repin: > ForwardToSyslog=yes this is long obsolete $WorkDirectory /var/lib/rsyslog module(load="imjournal" StateFile="imjournal.state" WorkAroundJournalBug="on" Ratelimit.Interval="600" Ratelimit.Burst="5")

Re: [systemd-devel] Journal message timestamps

Am 08.09.20 um 13:06 schrieb Mark Corbin: > Change /lib/systemd/system/fake-hwclock.service to add > 'systemd-journald.service' to the end of the 'Before' line this is *system* area and the admin has no business to touch anything there as well as packages have no business to touch admin area

Re: [systemd-devel] Q: Start a unit n minutes after a successful boot

Am 08.09.20 um 09:21 schrieb Ulrich Windl: > Configuring a new system with non-redundant system disk I'm wondering: How > could I start an automatic backup job that is triggered n minutes after the > system started * create a own target * order it after multi-user.target * put a service jn

Re: [systemd-devel] Antw: [EXT] Re: Using timedatectl on a readonly rootfile system using mender

Am 07.09.20 um 10:52 schrieb Ulrich Windl: Vito Caputo schrieb am 05.09.2020 um 04:44 in Nachricht > <20200905024407.n2qy34rxqqdlv...@shells.gnugeneration.com>: >> Could you please stop signing mails sent to this publicly accessible, >> archived, and indexed/searchable mailing list

Re: [systemd-devel] Antw: [EXT] Re: User/Group overrides in a templated service triggered via timer

Am 07.09.20 um 10:00 schrieb Ulrich Windl: >> Anyway, long story short: you typically do not enable services that >> are only supposed to activated by timer units, enabling those timers >> should entirely suffice, and the timers will start the services when >> the time comes. > > Interesting:

Re: [systemd-devel] systemd-userdbd and other stuff running all the time

Am 04.09.20 um 17:52 schrieb Reindl Harald: > Am 04.09.20 um 17:37 schrieb Lennart Poettering: >> userdbd is activated on demand and exit-on-idle btw. it exits after >> 25s of no client making any request. if you have it running this means >> stuff is using it. well,

Re: [systemd-devel] howto switch from grub2-bios to systemd-boot

Am 04.09.20 um 17:44 schrieb Lennart Poettering: > On Fr, 04.09.20 17:10, Reindl Harald (h.rei...@thelounge.net) wrote: > >>> No, that's not supported in sd-boot. A boot loader is a boot loader, >>> it should contain a fragile storage stack. It's kinda what sd-boot is &

Re: [systemd-devel] systemd-userdbd and other stuff running all the time

Am 04.09.20 um 17:37 schrieb Lennart Poettering: > On Mo, 24.08.20 13:40, Reindl Harald (h.rei...@thelounge.net) wrote: > >> is taht growing amount of services running on all systems really >> necessary and why are things like "repart.service" and "homed.servi

Re: [systemd-devel] howto switch from grub2-bios to systemd-boot

Am 04.09.20 um 16:58 schrieb Lennart Poettering: > On Mo, 22.06.20 16:01, Reindl Harald (h.rei...@thelounge.net) wrote: > >> what is the best way to get a Fedora using legacy-boot to UEFI and at >> the same time switch from grub2 to systemd-boot? >> >> * how to ge

Re: [systemd-devel] Any published books on systemd? A cookbook?

Am 29.08.20 um 19:17 schrieb Tom Browder: > On Fri, Aug 28, 2020 at 11:12 Andrei Borzenkov > wrote: > > 28.08.2020 17:47, Tom Browder пишет: > > I want to create a service file that has to consider other services. > > ... > > If you tell us what you

Re: [systemd-devel] A sh -c '${name} and $name' are treated inconsistently within a .service unit

Am 27.08.20 um 18:11 schrieb u...@net9.ga: > [Unit] > Description=Is it looking for ${} construct in the wrong place? > [Service] > Type=oneshot > ExecStart=/bin/bash -c 'set -x; declare -r str="1 2"; echo ${str}; echo $str; > exit 0;' > > When ran, the journal has: > > bash[14190]: +

Re: [systemd-devel] Antw: [EXT] Re: tmpfiles chicken-egg problem

Am 26.08.20 um 16:01 schrieb Ulrich Windl: Lennart Poettering schrieb am 26.08.2020 um 15:40 > in > Nachricht <20200826134031.GA257903@gardel-login>: >> On Mi, 26.08.20 08:37, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) > wrote: >> >>> Hi! >>> >>> I see this problem in SLES12

Re: [systemd-devel] 'PIDFile=' warning and override.conf

Am 26.08.20 um 11:48 schrieb Richard Hector: > On 26/08/20 9:07 pm, Reindl Harald wrote: >> >> >> Am 26.08.20 um 01:26 schrieb Richard Hector: >>> Hi all, >>> >>> I've got the common warning: >>> >>> /lib/systemd/system/fail2b

Re: [systemd-devel] tmpfiles chicken-egg problem

Am 26.08.20 um 08:37 schrieb Ulrich Windl: > I see this problem in SLES12 (systemd-228-157.12.5.x86_64): On boot systemd > tries to use LDAP to resolve user names, resulting in an error like this: > systemd-tmpfiles: nss-ldap: do_open: do_start_tls failed:stat=-1 > > Eventually: >

Re: [systemd-devel] 'PIDFile=' warning and override.conf

Am 26.08.20 um 01:26 schrieb Richard Hector: > Hi all, > > I've got the common warning: > > /lib/systemd/system/fail2ban.service:12: PIDFile= references path below > legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → > /run/fail2ban/fail2ban.pid; please update the unit file

[systemd-devel] systemd-userdbd and other stuff running all the time

is taht growing amount of services running on all systems really necessary and why are things like "repart.service" and "homed.service" are started "static" which makes the concept of enable/disable things more and more obsolete 7.4 MB is a lot and i don't see any issue by just mask

Re: [systemd-devel] Need help with setting up systemd for Apache on Debian 10

Am 23.08.20 um 19:19 schrieb Tom Browder: > There is no official Apache systemd setup for Apache from source, and > I didn't get any help from users there. I tried to mimic a good > solution by first installing Apache with the Debian package and > finding all the systemd files with "httpd" or

Re: [systemd-devel] fuse-sshfs and x-systemd.automount

Am 16.08.20 um 17:22 schrieb Lennart Poettering: > On So, 16.08.20 17:14, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Am 16.08.20 um 17:03 schrieb Lennart Poettering: >>> On Sa, 15.08.20 22:56, Reindl Harald (h.rei...@thelounge.net) wrote: >>> >&

Re: [systemd-devel] fuse-sshfs and x-systemd.automount

Am 16.08.20 um 17:21 schrieb Lennart Poettering: > On So, 16.08.20 17:16, Reindl Harald (h.rei...@thelounge.net) wrote: >> Am 16.08.20 um 17:01 schrieb Lennart Poettering: >>> On So, 16.08.20 09:05, Reindl Harald (h.rei...@thelounge.net) wrote: >>> >>>> ho

Re: [systemd-devel] fuse-sshfs and x-systemd.automount

Am 16.08.20 um 17:01 schrieb Lennart Poettering: > On So, 16.08.20 09:05, Reindl Harald (h.rei...@thelounge.net) wrote: > >> how is it not given it#s a systemd-option and what is your f** >> problem? > > Reindl, I'll put you back on moderation if you write another ma

Re: [systemd-devel] fuse-sshfs and x-systemd.automount

Am 16.08.20 um 17:03 schrieb Lennart Poettering: > On Sa, 15.08.20 22:56, Reindl Harald (h.rei...@thelounge.net) wrote: > >> is it a bug or a concept issue that it's mounted fpr root instead auf >> the user given with uid or is there just a param i am not aware >&

Re: [systemd-devel] fuse-sshfs and x-systemd.automount

Am 16.08.20 um 07:51 schrieb Andrei Borzenkov: > 15.08.2020 23:56, Reindl Harald пишет: >> is it a bug or a concept issue that it's mounted fpr root instead auf >> the user given with uid or is there just a param i am not aware mising? > > allow_other works, but chan

Re: [systemd-devel] systemd-inhibit don't work

Am 10.08.20 um 15:37 schrieb Lennart Poettering: > On Mo, 10.08.20 15:05, Reindl Harald (h.rei...@thelounge.net) wrote: > >> well, i would expect that the reboot in the scond ssh-session is >> refused... >> >> [root@master:~]$ /usr/bin/systemd-inhibit --wha

[systemd-devel] systemd-inhibit don't work

well, i would expect that the reboot in the scond ssh-session is refused... [root@master:~]$ /usr/bin/systemd-inhibit --what=shutdown --who=root --why="Backup in progress" --mode=block sleep 600 [root@master:~]$ /usr/bin/systemd-inhibit; systemctl reboot WHO UID USER PID COMM

Re: [systemd-devel] nested x-systemd.automount - parent always mounted

Am 28.07.20 um 12:05 schrieb Lennart Poettering: > On Di, 28.07.20 02:02, Reindl Harald (h.rei...@thelounge.net) wrote: > >> Hi >> >> is this a kernel limitation or could systemd act better by *not* mount >> /boot unconditional becasue of the inherited /boot/efi?

  1   2   3   4   5   6   7   8   9   10   >