| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Schout <mschout(at)gkg(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 7.0 RPMS and syslog problem. (more) |
| Date: | 2000-05-17 16:55:59 |
| Message-ID: | 3922CF1F.DBEC27DB@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Michael Schout <mschout(at)gkg(dot)net> writes:
> > Upon further investigation, I found that when the hostname is broadcast to everyone, the following also appears in /var/log/messages:
> > May 17 09:28:11 galaxy
> > May 17 09:28:11 galaxy syslogd: Cannot glue message parts together
> Hmm. We were just discussing this a few weeks ago, when someone
> suggested making the syslog option be the default and I wanted to
> know if it was really robust enough for that. Seems it's not.
> So I'm afraid the answer is that syslog and verbose logging won't
> play together, at least not on your platform. Sorry.
> We really need a better logging answer...
Splitting the logging message out to syslog in tprintf() (or its
replacement) would work, if we knew the syslog gluing buffer maxlen. A
'packetized' logging system of this sort might work....
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitch Vincent | 2000-05-17 16:57:19 | Re: Ouch .. VACUUM *is* killer ... |
| Previous Message | The Hermit Hacker | 2000-05-17 16:47:25 | Re: Ouch .. VACUUM *is* killer ... |