On Mon, Feb 08, 2021 at 11:43:35AM +0200, Vlad Zahorodnii wrote:
> Hi,
> My question is - should Wayland compositors handle logind restarts
> in any way?
>
> At the moment, many Wayland compositors don't take any precautions
> against the case where logind is restarted. They assume that the DRM
>>> Phillip Susi schrieb am 05.02.2021 um 16:02 in
Nachricht
<87a6si5yjq@vps.thesusis.net>:
> Chris Murphy writes:
>
>> But it gets worse. The way systemd‑journald is submitting the journals
>> for defragmentation is making them more fragmented than just leaving
>> them alone.
>
> Wait,
>>> 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 to start the service and its sockets at a
Hi,
Currently, a lot of Wayland compositors can't recover from logind
restarts. For example, that's the case with weston, sway, kwin, and
perhaps other compositors.
The culprit seems to be that atomic commits fail with the "Permission
denied" error.
My question is - should Wayland
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
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 on demand, and it's a good idea to use them
On So, 07.02.21 22:43, Reindl Harald (h.rei...@thelounge.net) wrote:
> 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
08.02.2021 12:10, Ulrich Windl пишет:
> It seems systemd messes with that in a bad way.
>
Streetlight effect ...
For the last time - systemd does exactly what unit definitions tell it
to do. Unit definitions belong to your application. If unit definitions
that come with application are not
On Sa, 06.02.21 12:51, Chris Murphy (li...@colorremedies.com) wrote:
> The original commit description only mentions COW, it doesn't mention
> being predicated on nodatacow. In effect commit
> f27a386430cc7a27ebd06899d93310fb3bd4cee7 is obviated by commit
>
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
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 broken.
>
> No I'm suggesting there isn't currently a way to isolate
> defragmentation to just HDDs.
Yes, but it sounded like you
Chris Murphy writes:
> I showed that the archived journals have way more fragmentation than
> active journals. And the fragments in active journals are
> insignificant, and can even be reduced by fully allocating the journal
Then clearly this is a problem with btrfs: it absolutely should not
On Sa, 06.02.21 19:47, Chris Murphy (li...@colorremedies.com) wrote:
65;6201;1c
> On Fri, Feb 5, 2021 at 8:23 AM Phillip Susi wrote:
>
> > Chris Murphy writes:
> >
> > > But it gets worse. The way systemd-journald is submitting the journals
> > > for defragmentation is making them more fragmented
On Fr, 05.02.21 17:44, Chris Murphy (li...@colorremedies.com) wrote:
> On Fri, Feb 5, 2021 at 3:55 PM Lennart Poettering
> wrote:
> >
> > On Fr, 05.02.21 20:58, Maksim Fomin (ma...@fomin.one) wrote:
> >
> > > > You know, we issue the btrfs ioctl, under the assumption that if the
> > > > file is
On Mo, 08.02.21 10:09, Phillip Susi (ph...@thesusis.net) wrote:
> That's a fair point: if btrfs isn't any worse than other filessytems,
> then why is it the only one that gets a defrag?
As answered elsewhere:
1. only btrfs has a cow mode, where fragmentation is through the roof
for randomly
On 2/8/21 7:52 AM, Uoti Urpala wrote:
This is wrong. Socket units are useful completely independently of
whether the unit is started on demand, and it's a good idea to use them
even for services that are always started on boot. They allow
configuring listening ports in a consistent manner, and
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 to
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
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 your actual issue, ignoring all
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?id=1909805#c6
It almost works
On Mon, Feb 8, 2021 at 8:20 AM Phillip Susi wrote:
>
>
> Chris Murphy writes:
>
> > I showed that the archived journals have way more fragmentation than
> > active journals. And the fragments in active journals are
> > insignificant, and can even be reduced by fully allocating the journal
>
>
>>> Andrei Borzenkov schrieb am 08.02.2021 um 19:43 in
Nachricht <63608ba2-0510-0e03-eb20-c92d86521...@gmail.com>:
> 08.02.2021 12:10, Ulrich Windl пишет:
>> It seems systemd messes with that in a bad way.
>>
>
> Streetlight effect ...
>
> For the last time - systemd does exactly what unit
On 2/8/21 12:55 PM, Zbigniew Jędrzejewski-Szmek wrote:
The culprit seems to be that atomic commits fail with the
"Permission denied" error.
That's because of a bug in logind. I started working on a fix last
year [1], but doing this properly requires restructuring how the code
handles cleanup.
>>> 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 to your actual issue,
Hi everyone,
I am trying to setup an app using transparent proxy and I need to insert the
following route:
ip route add local 0.0.0.0/0 dev lo table 100
After a few attempts, I noticed that it appears that systemd-networkd, on my
router, cannot insert any route to any table other than the
On Mon, Feb 8, 2021 at 1:24 AM Ulrich Windl
wrote:
>
> I didn't follow the thread tightly, but there was a happy mix of IOps,
> fragments (and no bandwidth),
> but I wonder here: Isn't it concept of BtrFS that writes are fragmented if
> there is no contiguous free space?
> The idea was *not* to
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 broken.
> >
> > No I'm suggesting there isn't currently a way to isolate
27 matches
Mail list logo
