| From: | "Cory 'G' Watson" <gphat(at)loggerithim(dot)org> |
|---|---|
| To: | Doug McNaught <doug(at)mcnaught(dot)org> |
| Cc: | Errol Neal <errol(dot)neal(at)enhtech(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Solaris, Postgresql and Problems |
| Date: | 2003-07-25 15:31:27 |
| Message-ID: | 0E6DDAFA-BEB5-11D7-8233-0003939CCA58@loggerithim.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday, July 25, 2003, at 10:15 AM, Doug McNaught wrote:
> This means *something* is sending a SIGTERM to the postmaster. Again,
> try running it under 'truss' and see what it's doing right before it
> gets the signal.
Also, make sure you are starting it in a way that you can _see_ the
error. Use something like
postmaster -D /usr/local/pgsql/data
If you are using a startup script or something similar, you may not see
the error in your terminal.
I often have this problem after changing system settings.
Cory 'G' Watson
http://www.loggerithim.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Weiping He | 2003-07-25 15:34:18 | Re: Solaris, Postgresql and Problems |
| Previous Message | Benjamin Jury | 2003-07-25 15:23:40 | Re: How to encrypt data in Postgresql |