From: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: server auto-restarts and ipcs |
Date: | 2004-11-09 16:54:59 |
Message-ID: | 1100019299.29685.62.camel@linda |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tue, 2004-11-09 at 07:00 -0700, Ed L. wrote:
> On Tuesday November 9 2004 2:16, Oliver Elphick wrote:
> > On Mon, 2004-11-08 at 17:47 -0700, Ed L. wrote:
> > > I often wonder why ipcs never seems to show the shared memory
> > > block in question?
> >
> > The permissions of the shared memory block and the semaphore arrays are
> > 600. ipcs seems not to report objects which you cannot access. Run
> > ipcs as root and you should see the PostgreQSL shared memory segment and
> > semaphores.
>
> I don't see them when running ipcs as root, either. Not sure that would
> make sense given the shared memory is created as the same user running
> ipcs...
If neither root nor their creator can see them, I assume they don't
exist. Certainly, with Linux 2.6 and util-linux 2.12, ipcs sees the
postgres objects whether it is run by root or by the postgres user.
--
Oliver Elphick olly(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA
========================================
"O death, where is thy sting? O grave, where is
thy victory?" 1 Corinthians 15:55
From | Date | Subject | |
---|---|---|---|
Next Message | Ron St-Pierre | 2004-11-09 17:07:08 | Re: INTERVAL in a function |
Previous Message | Markus Schaber | 2004-11-09 16:49:00 | Re: Avoiding explicit addDataType calls for PostGIS |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-11-09 17:00:46 | Re: Reorganization of the translation files |
Previous Message | Peter Eisentraut | 2004-11-09 16:30:09 | Reorganization of the translation files |