Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Currently the syslog writes to a fifo, from which a cronjob reads, and therefor empty the fifo.
For several hours, I will need this job to be disabled, and then the fifo gets full pretty quick.
Will increasing the log_fifo_size to a higher value solve this issue, so it will buffer the log, until the fifo is ready to be written to again?
Currently the syslog writes to a fifo, from which a cronjob reads, and therefor empty the fifo.
For several hours, I will need this job to be disabled, and then the fifo gets full pretty quick.
Will increasing the log_fifo_size to a higher value solve this issue, so it will buffer the log, until the fifo is ready to be written to again?
^.*syslog.*$ is for (reasonably) reliable logging of messages to a (any) destination. So unless these messages are expendable in the first place it does not make sense for a destination to be unavailable. So unless you're working with some exotic scenario you haven't told us about I would suggest only loading output filter when needed.
Maybe start by explaining what you need to do (what's the actual purpose for having a cron job disabled for hours) and why you chose to do it this way (cron job reading fifo)?
With all respect, this is not really relevant to the question.....
But, it reads log files and insert these into a DB... This cannot currently be changed, because it will require a lot rewrite of code, and/or new setup in a production environment.
A good understanding of a problem may lead to proper analysis which in turn may lead to being able to offer suitable solutions. As you're not willing to explain your situation properly no analysis is possible. So I'll leave you remarking that Rsyslog has disk queues and disk-assisted memory queues, can read from about any log file and write CSV output or write to databases directly. Good luck.
Yes, I am aware that other solutions is better, like writing to the SQL Server directly, but that is not an option here. It could be, but as mentioned it would require a LOT of rewrite of the code base, and a new setup for which this log is used, which is unfortunately not an option at this point.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
