Re: [HACKERS] IPC Memory problem with Postmaster on BSDi 4.x
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] IPC Memory problem with Postmaster on BSDi 4.x |
Дата | |
Msg-id | 199907311653.MAA27689@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] IPC Memory problem with Postmaster on BSDi 4.x (Roberth Andersson <roberth@jump-gate.com>) |
Список | pgsql-hackers |
> >I am running BSDI here. Try using pgsql/bin/ipcclean to remove the > >current shared memory stuff. Seems the old version did not clean up its > >shared memory. > > Thanks Bruce > > I tried to do that and it worked just fine the first time, and after that I > wrote "ipcs" to get a statistical if it really was cleaned or not, but I > got this -> > > Message Queues: > T ID KEY MODE OWNER GROUP > > Shared Memory: > T ID KEY MODE OWNER GROUP > m 1376259 0 --rwa------ postgres postgres > m 131076 0 --rw------- postgres user > m 786437 0 --rw------- postgres postgres > > Semaphores: > T ID KEY MODE OWNER GROUP > > Now I tried to use "ipcclean" once again, and I am always getting these > errors -> > > ipcrm: shmid(1376259): : Invalid argument > ipcrm: shmid(131076): : Invalid argument > ipcrm: shmid(786437): : Invalid argument > > I have no idea why, except maybe this could be something that is left over > since old and now the system doesn't know how to remove this Postgres stuff. > > If anyone have any clue about what I can do, please let me know, I would > appreciate it a lot. Go to /tmp, and do a ls -la. There will be some file in there that are left over that should be deleted. But now that I look, they aren't in /tmp anymore in 4.0. Use ipcs and ipcrm to manually delete them. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: