Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor multiple parsing of same log file #529

Open
grooverdan opened this issue Dec 28, 2013 · 2 comments
Open

refactor multiple parsing of same log file #529

grooverdan opened this issue Dec 28, 2013 · 2 comments

Comments

@grooverdan
Copy link
Contributor

Users are using the same log file like mail.log for multiple jails. It may make sense to move all the time parsing there perhaps FileContainer.readline (with some per jail position).

@ghost ghost assigned grooverdan Dec 28, 2013
@kwirk kwirk modified the milestones: 0.9.2, 0.9.1 May 7, 2014
@yarikoptic yarikoptic modified the milestones: 0.9.2, 0.9.3 Feb 14, 2015
@grooverdan grooverdan removed their assignment Jul 9, 2015
@yarikoptic yarikoptic modified the milestones: 0.9.3, 0.9.4 Jul 11, 2015
@yarikoptic yarikoptic modified the milestones: 0.9.4, 0.9.5 Jan 8, 2016
@yarikoptic
Copy link
Member

@sebres I wondered if 0.10 doesn't do smth like that already? ;-)

@yarikoptic yarikoptic removed this from the 0.9.5 milestone Jun 20, 2016
@sebres
Copy link
Contributor

sebres commented Jun 20, 2016

Unfortunately not :(

But it was planned, because as I made an observer module (ban-time-incr), which thread work totally event driven, I've realized also that we can and should separate the monitoring functionality to different thread pool, that will notify action/filter pool doing the processing actions only (banning, unbanning etc.)

I don't think, that it is currently a great problem, as long as the monitored log-lines still not washed out from system cache, but I'll nevertheless appreciate if we have done such refactoring.

Maybe together with #1379 (or after it will be ready)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants