Don't check memory status when detaching shmem segment.  Actually this basic logic is broken in shmmodule, because it is possible for a segment to be destroyed (or rather marked for destruction) which means it technically doesn't exist, but it should otherwise function fine for any processes that have attached it.  I'll revisit this code later, but for now this change allows us to detach from a shmem segment after it has been marked for destruction in another process.
Don't check memory status when detaching shmem segment.  Actually this basic
logic is broken in shmmodule, because it is possible for a segment to be
destroyed (or rather marked for destruction) which means it technically
doesn't exist, but it should otherwise function fine for any processes
that have attached it.  I'll revisit this code later, but for now this
change allows us to detach from a shmem segment after it has been marked
for destruction in another process.


git-svn-id: 9d763a2146cc7918956fa045a5de4b112f309167@1819 a8f5125c-1e01-0410-8897-facf34644b8e

freevo/kaa-base,freevo/kaa-base