On Tue, 10 May 2016, Nelson A. de Oliveira wrote: > Hi!
> On Tue, May 10, 2016 at 9:36 AM, Yaroslav Halchenko <y...@debian.org> 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 services takes a while to kick off? > From what I understand with the attached SVG file the network.target > is alread active and fail2ban.service takes +10s to activate. in svg it indeed looks like that... so provide details such as /var/log/fail2ban.log (possibly with higher log level). http://www.fail2ban.org/wiki/index.php/HOWTO_Seek_Help could be of help. the only thing which could lead to such slow start up is abundance of log files to get through but I thought that it would be done in background... so -- how many and how big are the files you are monitoring? -- 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
