What do you get for:
sudo systemctl status earlyoom.service
I see:
Loaded: loaded (/usr/lib/systemd/system/earlyoom.service;
disabled; vendor preset: disabled)
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
On 23.05.2021 19:05, Neal Gompa wrote:
Actually, it is. That trigger is wrong:
It should work fine.
Version in Fedora 33: earlyoom-1.6.2-1.fc33.
Version in Fedora 34: earlyoom-1.6.2-3.fc34.
The trigger is: earlyoom < 1.6.2-3
It will be automatically executed on F34 upgrade. I tested it in VM
On 23.05.2021 19:05, Neal Gompa wrote:
Actually, it is. That trigger is wrong:
https://src.fedoraproject.org/rpms/earlyoom/pull-request/3
It should be instead: %triggerun -- fedora-release-common < 34
Should I fix this?
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
On Sun, May 23, 2021 at 12:45 PM Vitaly Zaitsev via devel
wrote:
>
> On 23.05.2021 16:00, Neal Gompa wrote:
> > This is a bug and needs to be fixed.
>
> This is not an earlyoom's bug:
>
> https://src.fedoraproject.org/rpms/earlyoom/blob/rawhide/f/earlyoom.spec#_44
>
Actually, it is. That trigger
On 23.05.2021 16:00, Neal Gompa wrote:
This is a bug and needs to be fixed.
This is not an earlyoom's bug:
https://src.fedoraproject.org/rpms/earlyoom/blob/rawhide/f/earlyoom.spec#_44
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
devel
El dom, 23 may 2021 a las 11:01, Neal Gompa () escribió:
> On Sun, May 23, 2021 at 9:59 AM Sergio Belkin wrote:
> >
> > Hi,
> > I've upgraded from F33 to F34 using dnf plugin and I've found that both
> systemd-oomd and earlyoom service are running:
> >
> > systemctl is-active earlyoom.service sys
On Sun, May 23, 2021 at 9:59 AM Sergio Belkin wrote:
>
> Hi,
> I've upgraded from F33 to F34 using dnf plugin and I've found that both
> systemd-oomd and earlyoom service are running:
>
> systemctl is-active earlyoom.service systemd-oomd.service
> active
> active
>
> and:
>
> systemctl is-active
Hi,
I've upgraded from F33 to F34 using dnf plugin and I've found that both
systemd-oomd and earlyoom service are running:
systemctl is-active earlyoom.service systemd-oomd.service
active
active
and:
systemctl is-active earlyoom.service systemd-oomd.service
active
active
Is this behaviour expec
