| From: | Vivek Khera <khera(at)kcilink(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Log files, how to rotate properly |
| Date: | 2001-06-15 18:08:58 |
| Message-ID: | x7u21hvcn9.fsf@onceler.kciLink.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "LO" == Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
LO> Then whose fault is that? Is it our syslog calling, or the
LO> receiving syslog not hearing? (Yes, I know that by default syslog
LO> uses UDP)....
Not on FreeBSD (probably most other BSD's as well), the default is to
use a named pipe.
Anyhow what is the best way to make postgres stop stderr logging when
syslog logging is turned on? Right now I use "-l /dev/null" to pg_ctl
when starting the server. This seems to me that the server will still
waste cycles doing the stderr printing.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric Ridge | 2001-06-15 18:11:50 | RE: Indexing varchar[]'s |
| Previous Message | Eric Ridge | 2001-06-15 18:04:42 | RE: Indexing varchar[]'s |