On Tue, 10 May 2016, Nelson A. de Oliveira wrote:
> Hi!
> On Tue, May 10, 2016 at 9:36 AM, Yaroslav Halchenko wrote:
> > isn't this suggesting that it has nothing to do with fail2ban start time
> > (which should be really fast since it just initiates a daemon in the
> > background) but rather t
Hi!
On Tue, May 10, 2016 at 9:36 AM, Yaroslav Halchenko wrote:
> isn't this suggesting that it has nothing to do with fail2ban start time
> (which should be really fast since it just initiates a daemon in the
> background) but rather that you 'network.target' an in particular
> networking service
On Tue, 10 May 2016, Nelson A. de Oliveira wrote:
> Package: fail2ban
> Version: 0.9.4-1
> Severity: normal
> I was seeing that fail2ban takes a long time to start when booting:
> =
> $ systemd-analyze blame
> 10.775s fail2ban.service
> (...)
> =
> (it's the top one)
> =
>
Package: fail2ban
Version: 0.9.4-1
Severity: normal
I was seeing that fail2ban takes a long time to start when booting:
=
$ systemd-analyze blame
10.775s fail2ban.service
(...)
=
(it's the top one)
=
$ systemd-analyze critical-chain
The time after the unit is active or start
4 matches
Mail list logo
