in reply to insert syslog log entries into MySQL?

As for 2, the answer is no. If you want persistency, use files (and even then there's still the possibility of data loss). The data "waiting" in a pipe is stored in memory - that's why pipes are faster than files.

As for 3., check your manual of syslog.conf. If it's possible on RH 9, it'll be in the manual. (This is no longer a Perl issue).

But I'm a bit surprised you're suffering from data loss. Sure, if a box crashes, last minute reports could be lost (even before syslogd gets the chance to figure out where it goes), but under normal conditions, this should be rare, as reading from a pipe should be pretty fast. You are continuously reading from the pipe, aren't you?

Abigail

  • Comment on Re: insert syslog log entries into MySQL?

Replies are listed 'Best First'.
Re: Re: insert syslog log entries into MySQL?
by hmerrill (Friar) on Oct 20, 2003 at 16:40 UTC
    Ok, pipes and persistence don't go together. But you might be right - maybe the risk of data loss is small enough not to worry about :) I'll have to give this some thought.

    I've read just about everything I can find on syslog including the manpages. I only presented question #3 because I saw an example (that I couldn't get working) of a person who wrote a C program and that's how he described getting it to work in the syslog.conf file - piping the syslog messages to his program. I'm not a C programmer so I don't know what's special about the way he did that to get it to work.

    Thanks!
[reply]

In Section Seekers of Perl Wisdom