PfBlockerNG 2.0 DNSBL Log Browser
-
I tested on 2 boxes and no problems to clear any log file from pfblockerNG log menu.
-
I tested on 2 boxes and no problems to clear any log file from pfblockerNG log menu.
And any env. data about your hardware(what), software(pfSense version), browser(brand), code correction(Y/N) ?
-
As noted on the wiki - keep the damned thing mounted RW all time if you are nanobsd with CF.
-
I decided to clear package out and install it again. So it resolved itself….
I suspect a file crosslink corruption on the first two installs with this cache issues BBcan177 mentioned in the other thread OR nanoBSD(ro). And all went with nanoBSD(ro) this time, but doktornotor you have a point there case (rw). Damned. It's a test what else ;)
-
Sadly, since 2.2.3, the read-only feature with a normal use case (CF or SD card) is just not usable. Could be removed altogether if you ask me, with the benefit of simplifying the code in a bunch of places. Having it enabled by default on nanobsd just makes for a crappy experience for a lot of unsuspecting users. UFS performance is completely abysmal with these kinds of devices.
-
This is becoming a PITA.
Behaviour is back. It ran for 3 hours again a new fresh install of 2.0 on nanoBSD 2.2.5(rw) and just tested I can not empty || download dnsbl.log, when just after install it could do it… only once ?It is for the file dnsbl.log, not the others. Any suggestions ?
-
I for one cannot see what's your constant need for removing the log.
-
I for one cannot see what's your constant need for removing the log.
Well, it's building up with 500KB/day and the /var in RAM is 65% of 58MB, so I wanted to test if I could flush it. Then I ran into this phenomenon.
Do you happen to know where the code starts, the filename, for the buttons in the log browser?
-
hda: There's a setting to limit the number of lines in the log file on the General tab. So, it won't really keep growing beyond that. Plus, babysitting the thing ain't useful way to keep the size limited either. The logs are in /var/log/pfblockerng directory. If the setting above-mentoned setting doesn't work for you, it should be fixed there, instead of deleting it manually.
-
There's a setting to limit the number of lines in the log file on the General tab…
Ah thanks, I overlooked the variable. That 20000 will be about 5MB and 10% /var increase and then no problem for me. I'll check if/how it pans out.