Hi, Is there anyway I can tell post action that when a process does a semget(1207963596, 1, 0666|IPC_CREAT) and does not release the semaphore what process actually locked it. i.e in mdb would a defunct process or parent process have a hook still into the memory segment. I have a situation where a process is trying to get the semaphore but errors as below from the truss 26883/12: 126.6253 semget(1224740810, 3, 0666|IPC_CREAT) = 19 26883/12: 126.6257 semop(19, 0xFE6B2F80, 2) Err#11 EAGAIN Thanks Al -- This message posted from opensolaris.org
Peter Telford - Solaris sustaining
2008-Feb-21 12:34 UTC
[dtrace-discuss] semaphores on solaris 8
DTrace isn''t available on Solaris 8 so that''s the first stumbling block. It''s a fair bet a previous instance of the application that fails to get the semaphore now "forgot" to release it. Is the application leaving cores or anything to suggest problems? Which application is it? Rgds Peter. Allan wrote:> Hi, > > Is there anyway I can tell post action that when a process does a > semget(1207963596, 1, 0666|IPC_CREAT) and does not release the semaphore what process actually locked it. i.e in mdb would a defunct process or parent process have a hook still into the memory segment. > > I have a situation where a process is trying to get the semaphore but errors as below from the truss > 26883/12: 126.6253 semget(1224740810, 3, 0666|IPC_CREAT) = 19 > 26883/12: 126.6257 semop(19, 0xFE6B2F80, 2) Err#11 EAGAIN > > Thanks > Al > > > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20080221/ba15a7a7/attachment.bin>