inetd service issue

[shikhar_1 · Accepted solution]

Hi Dennis,

Thanks for your reply and solution. Now after doing ipcrm -s 16390. Inetd services started and looks good.

Now I can see inetd services running after removing the semaphore with the given command.

Could you please let us know that inetd uses 0x01090522?

[root@ncsqas06:/home/sverma8]#
#-> ps -ef | grep -i inetd
root 25897 1 0 13:23:04 ? 0:00 /usr/sbin/inetd -l
root 12513 8464 0 14:06:22 pts/2 0:00 grep -i inetd

[root@ncsqas06:/home/sverma8]#


From the previous output I can see these outputs.

Thu Feb 21 07:27:50 2013 [8057] semget(0x1090522, 1, 0) .................................. = 16390 Thu Feb 21 07:27:50 2013 [8057] semctl(16390, 0, GETPID, 0) .............................. = 0

============
From old ipcs -s

IPC status from /dev/kmem as of Thu Feb 21 12:15:51 2013
T ID KEY MODE OWNER GROUP
Semaphores:
s 16390 0x01090522 --ra-r--r-- root root

Could you please let us know that inetd uses 0x01090522?

[Dennis Handly]

>Could you please let us know that inetd uses 0x01090522?

That is the semaphore key that is used in semget(2) to get the ID.

And tusc shows that inetd uses that key.  If you use "ipcs -sa", you should see the PID of inetd too.