| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | USE_SYSLOG ... useless? :) |
| Date: | 2000-05-08 13:09:14 |
| Message-ID: | Pine.BSF.4.21.0005081007070.87721-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Just lookign through elog.c to see how I can improve logging, so taht I
can get more information from the backend. We have the above mentioned
USE_SYSLOG in a few places:
pgsql% find . -name "*.[ch]" -exec grep USE_SYSLOG {} \; -print
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
./backend/utils/error/elog.c
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
#ifdef USE_SYSLOG
./backend/utils/misc/trace.c
But nowhere to actually define it (not even listed in config.h.in) ...
pg_options shows a 'syslog=2' capability, but, without SysLOG enabled, its
sort of useless ...
what I want to get is a PID/Timestamp in the log files ... suggestions?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-05-08 13:13:08 | FindExec: found "/pgsql/bin/postgres" using argv[0] |
| Previous Message | D'Arcy J.M. Cain | 2000-05-08 12:44:00 | Re: Re: It happened again: Server hung up solid |