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

2021-02-09 Thread Michael Chapman
On Tue, 9 Feb 2021, Michael Chapman wrote: [...] > Note that when you're using Pacemaker to manage a systemd service, you > should not enable the service in the normal way -- that is, the service > should not be started simply by virtue of it being in the Wants= list of > multi-user.target. The

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

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 09:15 in Nachricht <20675743-9521-cdca-1c58-d42de7117...@very.puzzling.org>: > On Tue, 9 Feb 2021, Michael Chapman wrote: > [...] >> Note that when you're using Pacemaker to manage a systemd service, you >> should not enable the service in the normal

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

2021-02-09 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 09.02.2021 um 10:14 in Nachricht : > On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl > wrote: >> >> Thanks and "back to the mess": If I use libvirtd.service instead of >> libvirtd-tls.socket, it does *not* open the TLS socket, even though the >> configuration file

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

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 09:09 in Nachricht : > On Tue, 9 Feb 2021, Ulrich Windl wrote: > [...] >> As for the drop‑ins: I neither know what those are expected to do, not who >> adds them at run time. See "documentation"... > > The 50‑pacemaker.conf drop‑ins are, as their name

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

2021-02-09 Thread Andrei Borzenkov
On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl wrote: > > Thanks and "back to the mess": If I use libvirtd.service instead of > libvirtd-tls.socket, it does *not* open the TLS socket, even though the > configuration file contains "listen_tls=1"... libvirtd --listen Did you read the link I gave

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

2021-02-09 Thread Michael Chapman
On Tue, 9 Feb 2021, Ulrich Windl wrote: [...] > > > > libvirt can be run without socket activation [2]. I strongly recommend you > > configure it this way if you intend to manage libvirt in Pacemaker. > > Yes, I'd like to! Any pointers? Follow the link. It's all described there.

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

2021-02-09 Thread Michael Chapman
On Tue, 9 Feb 2021, Ulrich Windl wrote: [...] > At what timne exactly? When pacemaker starts, or when the systemd using is > about to be started? Pacemaker adds the drop-in just before it starts the resource, and it removes the drop-in just after it stops the resource. It's entire purpose is to

[systemd-devel] Antw: [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-09 Thread Ulrich Windl
>>> Chris Murphy schrieb am 09.02.2021 um 06:13 in Nachricht : > On Mon, Feb 8, 2021 at 7:56 AM Phillip Susi wrote: >> >> >> Chris Murphy writes: >> >> >> It sounds like you are arguing that it is better to do the wrong thing >> >> on all SSDs rather than do the right thing on ones that aren't

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

2021-02-09 Thread Michael Chapman
On Tue, 9 Feb 2021, Ulrich Windl wrote: [...] > As for the drop-ins: I neither know what those are expected to do, not who > adds them at run time. See "documentation"... The 50-pacemaker.conf drop-ins are, as their name suggests, created by Pacemaker. Specifically, Pacemaker's systemd resource

[systemd-devel] Should services be able to run without /proc?

2021-02-09 Thread Antonius Frie
Hi! So this is kind of a follow-up to the thread in [1], and the corresponding PR in [2]. In short, the PR made some changes to allow for cases where /proc was not available in the mount namespace of the service, and added a test [3] to make sure that this would work. This test was later

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

2021-02-09 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 09.02.2021 um 10:28 in Nachricht <602255b402a10003e...@gwsmtp.uni-regensburg.de>: Andrei Borzenkov schrieb am 09.02.2021 um 10:14 in > Nachricht > : >> On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl >> wrote: >>> >>> Thanks and "back to the mess": If I use

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

2021-02-09 Thread Reindl Harald
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

2021-02-09 Thread Reindl Harald
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 to

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

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 11:28 in Nachricht <74f975f6-1ef2-ee64-bf95-415a5626...@very.puzzling.org>: > On Tue, 9 Feb 2021, Ulrich Windl wrote: > [...] >> OK, I tried (staring libvirtd.service with ‑‑listen and without ‑‑timout): >> Feb 09 10:59:23 h18 libvirtd[42540]: ‑‑listen

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

2021-02-09 Thread Michael Chapman
On Tue, 9 Feb 2021, Ulrich Windl wrote: [...] > OK, I tried (staring libvirtd.service with --listen and without --timout): > Feb 09 10:59:23 h18 libvirtd[42540]: --listen parameter not permitted with > systemd activation sockets, see 'man libvirtd' for further guidance > Feb 09 10:59:23 h18

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

2021-02-09 Thread Ulrich Windl
>>> Andrei Borzenkov schrieb am 09.02.2021 um 10:14 in Nachricht : > On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl > wrote: >> >> Thanks and "back to the mess": If I use libvirtd.service instead of >> libvirtd-tls.socket, it does *not* open the TLS socket, even though the >> configuration file

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

2021-02-09 Thread Ulrich Windl
>>> Michael Chapman schrieb am 09.02.2021 um 10:17 in Nachricht : > On Tue, 9 Feb 2021, Ulrich Windl wrote: > [...] >> At what timne exactly? When pacemaker starts, or when the systemd using is >> about to be started? > > Pacemaker adds the drop‑in just before it starts the resource, and it >

Re: [systemd-devel] [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-09 Thread Phillip Susi
Chris Murphy writes: > Basically correct. It will merge random writes such that they become > sequential writes. But it means inserts/appends/overwrites for a file > won't be located with the original extents. Wait, I thoguht that was only true for metadata, not normal file data blocks? Well,

[systemd-devel] Antw: Re: [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-09 Thread Ulrich Windl
>>> Phillip Susi schrieb am 09.02.2021 um 15:53 in >>> Nachricht <87o8gtz3m1@vps.thesusis.net>: > Chris Murphy writes: > >> Basically correct. It will merge random writes such that they become >> sequential writes. But it means inserts/appends/overwrites for a file >> won't be located with

Re: [systemd-devel] consider dropping defrag of journals on btrfs

2021-02-09 Thread Phillip Susi
Chris Murphy writes: > And I agree 8MB isn't a big deal. Does anyone complain about journal > fragmentation on ext4 or xfs? If not, then we come full circle to my > second email in the thread which is don't defragment when nodatacow, > only defragment when datacow. Or use BTRFS_IOC_DEFRAG_RANGE

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

2021-02-09 Thread 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 and the fuse module from being loaded

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

2021-02-09 Thread 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 > >>> wrote: > >

Re: [systemd-devel] [EXT] Re: consider dropping defrag of journals on btrfs

2021-02-09 Thread Chris Murphy
On Tue, Feb 9, 2021 at 8:02 AM Phillip Susi wrote: > > > Chris Murphy writes: > > > Basically correct. It will merge random writes such that they become > > sequential writes. But it means inserts/appends/overwrites for a file > > won't be located with the original extents. > > Wait, I thoguht

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

2021-02-09 Thread Mike Gilbert
On Tue, Feb 9, 2021 at 7:19 PM Mike Gilbert wrote: > > On Tue, Feb 9, 2021 at 7:05 PM Reindl Harald wrote: > > > > > > > > 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

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

2021-02-09 Thread Mike Gilbert
On Tue, Feb 9, 2021 at 7:05 PM Reindl Harald wrote: > > > > 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: >