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) > ===== > $ systemd-analyze critical-chain > The time after the unit is active or started is printed after the "@" > character. > The time the unit takes to start is printed after the "+" character. > graphical.target @22.067s > └─multi-user.target @22.067s > └─fail2ban.service @11.291s +10.775s > └─network.target @11.290s > └─networking.service @7.942s +3.344s > └─local-fs.target @7.908s > └─run-user-109.mount @21.426s > └─local-fs-pre.target @4.374s > └─keyboard-setup.service @2.493s +1.880s > └─system.slice @2.445s > └─-.slice @2.280s 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 services takes a while to kick off? -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
