>>>>> "LO" == Lamar Owen <lamar.owen@wgcr.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@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
