On Sat, Feb 03, 2007 at 08:23:25PM -0300, César Catrián Carreño wrote:
> I would like to know what people do with their orphaned shared memory
> segments.
> 
> SHMMAXPGS could be big, but after a lot of use, it gets filled. As
> example, sometimes opera and mplayer with X11's xv extension can't be
> used together.
> 
> ipcrm(1) remove those orphaned segments, but it requires sysadmin
> intervention.

sysV shared memory segments can be removed by the user who created them.

> I am talking about an X environment with remote, KDE users.
> 
> Do the processes close (mandatory) their shared memory segments when
> quitting?

no.

find the programs which are leaking shared memory segments and file bug
reports, or fix them.

are there cases where sysV shared memory is preferable to using
anonymous shared mmap() pages, or is this a case of legacy
compatibility?

-- 
  Aaron J. Grier | "Not your ordinary poofy goof." | agrier@poofygoof.com
              "silly brewer, saaz are for pils!"  --  virt