> Also, if your pipe reader slows down too much, syslogd will start
> blocking on the pipe
Indeed.
> So I think it'd be much safer to
> have a flat text logfile and have your program read from that
Or send the data to DB backend only when the logs are rotated. As long
as the logs are kept sho
KuroiNeko <[EMAIL PROTECTED]> writes:
> > I am not sure I understand the implications of the piping it to the
> > insert
> > routine.
>
> It's a double-edged sword. Invoking it is as simple as adding a line to a
> conf file, while developing it may turn out to be tricky. At least mak
> I am not sure I understand the implications of the piping it to the
> insert
> routine.
It's a double-edged sword. Invoking it is as simple as adding a line to a
conf file, while developing it may turn out to be tricky. At least make
sure you examine output of ps ax to see how much
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of KuroiNeko
> Sent: Monday, April 02, 2001 9:10 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Log file to sql database
>
>
> > Anyone care to share suggestions on getting
: [GENERAL] Log file to sql database
What kind of logs are you trying to dump to postgres? I recently used
firelogd to enter logs for iptables-based firewalls, and it's working
great.
On Mon, 2 Apr 2001, Joseph wrote:
>
> Anyone care to share suggestions on getting data from a running
