Re: Custom log file to alternative to db

[jimpudar]

I would probably use Fail2ban, but since you mentioned this is for fun here are a couple of ideas.

Multiple processes all writing to the same file can step on each other if you use the normal print function due to buffering issues. I have used syswrite in the past to get around this and it works well. However in my experience if the log messages are short, Log4perl works fine with multiple processes all writing to the same file. I only ran into problems when printing multiline messages several KB in length at the same time.

Another idea would be using a DBI driver that works with files instead of a full database such as DBD::CSV so you don't need to install a database but could easily drop one in later by switching to a different driver. However if you are on an OS without flock simultaneous writes may be an issue. I don't have any experience with this to share unfortunately. Looks like if you are using Linux you should be okay.

If you get something working, I'm sure a lot of people would have feedback for you if you post it.

Best,

Jim