Re: shmctl EIDRM preventing startup

Поиск
Список
Период
Сортировка
Искать
От
Martijn van Oosterhout
Тема
Re: shmctl EIDRM preventing startup
Дата
Msg-id
20070702110535.GC12254@svana.org
Ответ на
Список
Дерево обсуждения
shmctl EIDRM preventing startup Michael Fuhr <mike@fuhr.org>
Re: shmctl EIDRM preventing startup Alvaro Herrera <alvherre@commandprompt.com>
Re: shmctl EIDRM preventing startup Tom Lane <tgl@sss.pgh.pa.us>
Re: shmctl EIDRM preventing startup Martijn van Oosterhout <kleptog@svana.org>
Re: shmctl EIDRM preventing startup Michael Fuhr <mike@fuhr.org>
Re: shmctl EIDRM preventing startup Tom Lane <tgl@sss.pgh.pa.us>
Re: shmctl EIDRM preventing startup Michael Fuhr <mike@fuhr.org>
On Sun, Jul 01, 2007 at 10:39:01PM -0400, Tom Lane wrote:
> Alvaro Herrera  writes:
> > Maybe what is happening is that an entirely unrelated process created a
> > segment with that ID, attached to it, and then it was deleted.  I don't
> > know how to check however.
> 
> AFAIK, EIDRM should imply that the segment has been IPC_RMID'd but still
> exists because there are still processes attached to it.  So the thing
> to look for is processes still attached.  Not 100% sure how to do that,
> but I'm sure the info is exposed under /proc somehow...

If it's installed, this:

lsof |grep SYSV

Will list all processes attached to a SHM segemtn on the system. I
think ipcs can do the same. You can grep /proc/*/maps for the same
info.

Have a nice day,
-- 
Martijn van Oosterhout      http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
В списке pgsql-general по дате отправления
От: Dimitri Fontaine
Дата:
От: cha
Дата:
FAQ