On Fri, 2024-05-03 at 16:52 -0500, Richard Shaw wrote:
> On Fri, May 3, 2024 at 4:13 PM Patrick O'Callaghan
>
> wrote:
>
> > On Fri, 2024-05-03 at 13:08 -0400, Tom Rivers via users wrote:
> > > Until the fix is available, I've been able to get it running
> > > until
> > > the
> > > next system
On Fri, May 3, 2024 at 4:13 PM Patrick O'Callaghan
wrote:
> On Fri, 2024-05-03 at 13:08 -0400, Tom Rivers via users wrote:
> > Until the fix is available, I've been able to get it running until
> > the
> > next system reboot by doing the following:
> >
> > # setenforce 0
> > # systemctl start
On Fri, 2024-05-03 at 13:08 -0400, Tom Rivers via users wrote:
> Until the fix is available, I've been able to get it running until
> the
> next system reboot by doing the following:
>
> # setenforce 0
> # systemctl start fail2ban
>
> ... wait a minute ...
>
> # setenforce 1
>
That seems to
Until the fix is available, I've been able to get it running until the
next system reboot by doing the following:
# setenforce 0
# systemctl start fail2ban
... wait a minute ...
# setenforce 1
Tom
On 5/3/2024 12:39 PM, Patrick O'Callaghan wrote:
On Fri, 2024-05-03 at 06:45 -0500, Richard
On Fri, 2024-05-03 at 06:45 -0500, Richard Shaw wrote:
> On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan
>
> wrote:
>
> > F40 fully updated.
> >
>
> Try a `dnf --refresh update`. The fix just went to stable last night.
That just gets the same update I already tried.
poc
--
On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan
wrote:
> F40 fully updated.
>
Try a `dnf --refresh update`. The fix just went to stable last night.
Thanks,
Richard
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an
