Re: Syslog and pg_options (for RPMs)

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: "Dominic J(dot) Eidson" <sauron(at)the-infinite(dot)org>
Cc: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Massimo Dal Zotto <dz(at)cs(dot)unitn(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Syslog and pg_options (for RPMs)
Date: 2001-02-08 21:14:34
Message-ID: Pine.GSO.4.33.0102090009470.22966-100000@ra.sai.msu.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 8 Feb 2001, Dominic J. Eidson wrote:

> On Thu, 8 Feb 2001, Lamar Owen wrote:
>
> > A syslogger of stderr would make a nice place to pipe the output :-).
> > 'postmaster .... 2>&1 | output-to-syslog-program -f facility.desired' or
> > some such. But that obviates the need to support syslog _at_all_ in the
>
> 2>&1 | logger -p facility.level

on linux box I got syslogd eats 45% of cpu.thats why I gave up and
use plain loging to file

>
> morannon:~> man logger
> LOGGER(1) System Reference Manual
> LOGGER(1)
>
> NAME
> logger - make entries in the system log
>
> SYNOPSIS
> logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [message ...]
>
> DESCRIPTION
> Logger provides a shell command interface to the syslog(3) system log
> module.
>
>
>

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Myers 2001-02-08 21:57:31 Re: Syslog and pg_options (for RPMs)
Previous Message Lamar Owen 2001-02-08 21:08:04 Re: Syslog and pg_options (for RPMs)