| From: | Andrew Sullivan <andrew(at)libertyrms(dot)com> |
|---|---|
| To: | Larry Rosenman <ler(at)lerctr(dot)org> |
| Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)com>, PostgreSQL general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: --enable-syslog and Solaris 7 |
| Date: | 2001-08-30 14:26:56 |
| Message-ID: | 20010830102656.F24535@mail.libertyrms.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Aug 30, 2001 at 09:07:32AM -0500, Larry Rosenman wrote:
> * Andrew Sullivan <andrew(at)libertyrms(dot)com> [010830 08:54]:
> Any chance syslogd is running up against a file limit of some kind to
> get the file open?
I can't see what; this is on a little test box, and nothing else is
running.
> And the file exists and has the correct permissions?
In desperation, I've opened it up completely, still with no joy:
-rwxrwxrwx 1 root other 0 Aug 30 08:53 pg.log
I also had it owned by postgres at one point. Anyway, I don't think
it can be a file problem, because running syslogd with debug on
doesn't show anything coming _in_ from postgres (unless I kill the
server with a client connected, because that throws a FATAL exception
which is caught). That suggests to me it must have something to do
with the facility that postgres is sending to, or my config file.
I'm really stumped.
> I do know the syslog code works, I use it heavily on my
> UnixWare/ÓpenUNIX and FreeBSD boxen.
I've used it elsewhere, too, which is why I'm so puzzled.
A
--
----
Andrew Sullivan 87 Mowat Avenue
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)com> M6K 3E3
+1 416 646 3304 x110
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2001-08-30 14:32:25 | Re: --enable-syslog and Solaris 7 |
| Previous Message | Larry Rosenman | 2001-08-30 14:07:32 | Re: --enable-syslog and Solaris 7 |