<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Inetd Hanging in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531826#M221602</link>
    <description>hi,&lt;BR /&gt;&lt;BR /&gt;the -b option is a toggle which turns debug on and off. what is option running on inetd"&lt;BR /&gt;&lt;BR /&gt;# ps -ef|grep -i inetd&lt;BR /&gt;&lt;BR /&gt;also, r there the patches for the other 11.0 similar to this server.&lt;BR /&gt;&lt;BR /&gt;regards.</description>
    <pubDate>Tue, 26 Apr 2005 03:22:18 GMT</pubDate>
    <dc:creator>Joseph Loo</dc:creator>
    <dc:date>2005-04-26T03:22:18Z</dc:date>
    <item>
      <title>Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531822#M221598</link>
      <description>I'm having a little trouble with inetd on one of my HP-UX 11.0 servers.&lt;BR /&gt;&lt;BR /&gt;Even though the configuration files (/etc/inittab, /etc/inetd.conf and /etc/rc.config.d/netdaemons) and versions of the binaries match the other 11.0 servers on our network, this one particular box is showing rather strange behaviour.&lt;BR /&gt;&lt;BR /&gt;When restarting inetd, inetd hangs until you issue the "inetd -b" command - it then works normally.&lt;BR /&gt;&lt;BR /&gt;Restarting the process (and even rebooting the server) seems to make no difference - inetd still hangs until it gets the -b switch !!&lt;BR /&gt;&lt;BR /&gt;HELP !?!?!?!?!</description>
      <pubDate>Tue, 26 Apr 2005 02:59:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531822#M221598</guid>
      <dc:creator>Paul Murray_4</dc:creator>
      <dc:date>2005-04-26T02:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531823#M221599</link>
      <description>Do you have any entries in syslog?</description>
      <pubDate>Tue, 26 Apr 2005 03:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531823#M221599</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-04-26T03:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531824#M221600</link>
      <description>Hi Alex - the only syslog messages written, hit the log after the "inetd -b" command is issued (before this, no messages are logged at all).&lt;BR /&gt;&lt;BR /&gt;However, the messages after issuing "inetd -b" are :-&lt;BR /&gt;&lt;BR /&gt;Apr 26 08:53:08 lndvs101 syslog: inetd sendsig: entered, sig=4&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: Extended connection logging enabled&lt;BR /&gt;Apr 26 08:53:08 lndvs101 syslog: inetd sendsig: exiting&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: protocol = tcp&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: telnet/tcp: Added service, server /usr/lbin/telnetd&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: ftp/tcp: Added service, server /usr/lbin/ftpd&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: login/tcp: Added service, server /usr/lbin/rlogind&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: shell/tcp: Added service, server /usr/lbin/remshd&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: exec/tcp: Added service, server /usr/lbin/rexecd&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: swat/tcp: Added service, server /opt/samba/bin/swat&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: cvspserver/tcp: Added service, server /usr/local/bin/cvs-server&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: rsync/tcp: Added service, server /usr/local/bin/rsync&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: protocol = tcp&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: Configuration complete&lt;BR /&gt;Apr 26 08:53:08 lndvs101 inetd[7227]: About to select()...&lt;BR /&gt;Apr 26 08:53:10 lndvs101 syslog: inetd sendsig: entered, sig=4&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Paul.&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Apr 2005 03:16:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531824#M221600</guid>
      <dc:creator>Paul Murray_4</dc:creator>
      <dc:date>2005-04-26T03:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531825#M221601</link>
      <description>If you have tusc, you can try and look what system calls make inetd hang with:&lt;BR /&gt;&lt;BR /&gt;tusc -f &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Do you have any additional lines that you added to inetd.conf? (even if they exist on other systems, it's still can cause problems here)</description>
      <pubDate>Tue, 26 Apr 2005 03:20:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531825#M221601</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-04-26T03:20:45Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531826#M221602</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;the -b option is a toggle which turns debug on and off. what is option running on inetd"&lt;BR /&gt;&lt;BR /&gt;# ps -ef|grep -i inetd&lt;BR /&gt;&lt;BR /&gt;also, r there the patches for the other 11.0 similar to this server.&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Tue, 26 Apr 2005 03:22:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531826#M221602</guid>
      <dc:creator>Joseph Loo</dc:creator>
      <dc:date>2005-04-26T03:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531827#M221603</link>
      <description>is the latest inetd patch (PHNE_28312)installed ?&lt;BR /&gt;&lt;BR /&gt;regards.&lt;BR /&gt;H</description>
      <pubDate>Tue, 26 Apr 2005 03:26:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531827#M221603</guid>
      <dc:creator>Henk Geurts</dc:creator>
      <dc:date>2005-04-26T03:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531828#M221604</link>
      <description>And another question:&lt;BR /&gt;How do you restart inetd?</description>
      <pubDate>Tue, 26 Apr 2005 03:27:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531828#M221604</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-04-26T03:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531829#M221605</link>
      <description>The current version of inetd is :-&lt;BR /&gt;&lt;BR /&gt;root@lndvs101..# what /usr/sbin/inetd&lt;BR /&gt;/usr/sbin/inetd:&lt;BR /&gt;         Copyright (c) 1983 Regents of the University of California.&lt;BR /&gt;        Revision: 1.12.214.3  Tue Aug  1 10:30:45 GMT 2000&lt;BR /&gt;        Patch id: PHNE_21835&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;When restarting, I've tried using the stopping and starting using the /sbin/init.d/inetd script, and also by running "inetd -k" and "/usr/sbin/inetd -l" commands manually.  Then, just to be paranoid, I've even tried rebooting the server.&lt;BR /&gt;&lt;BR /&gt;The odd thing is, this server is running the same patch levels as all of our 11.0 servers, but started showing this behaviour at the end of last week even though nothing has changed !!!&lt;BR /&gt;&lt;BR /&gt;Ok - slight update - I've just tried bouncing inetd again, but I couldn't get it to restart at all and had to reboot the server again.&lt;BR /&gt;&lt;BR /&gt;I've got the output from "tusc -f", but I'm not overly familiar with what it's telling me - should I be looking for anything specific ??&lt;BR /&gt;&lt;BR /&gt;(Thanks again for all the help !!!).&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Apr 2005 04:08:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531829#M221605</guid>
      <dc:creator>Paul Murray_4</dc:creator>
      <dc:date>2005-04-26T04:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531830#M221606</link>
      <description>If inetd hangs, you can attach here the last lines from tusc output. Those should be the last system calls that inetd executes before it hangs.</description>
      <pubDate>Tue, 26 Apr 2005 04:12:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531830#M221606</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-04-26T04:12:07Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531831#M221607</link>
      <description>Hi Alex - the last part of the tusc output is :-&lt;BR /&gt;&lt;BR /&gt;setaudid(0) ...................................................... = 0&lt;BR /&gt;sigsetreturn(0x7f7bcd56, 0x6211988, 1392) ........................ = 0&lt;BR /&gt;sigvec(SIGHUP, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGINT, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGQUIT, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGILL, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGTRAP, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGABRT, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGEMT, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGFPE, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGKILL, 0x7f7e0820, 0x7f7e082c) .......................... ERR#22 EINVAL&lt;BR /&gt;sigvec(SIGBUS, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGSEGV, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGSYS, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGPIPE, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGALRM, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGTERM, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGUSR1, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGUSR2, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGCLD, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGPWR, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGVTALRM, 0x7f7e0820, 0x7f7e082c) ........................ = 0&lt;BR /&gt;sigvec(SIGPROF, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGIO, 0x7f7e0820, 0x7f7e082c) ............................ = 0&lt;BR /&gt;sigvec(SIGWINCH, 0x7f7e0820, 0x7f7e082c) ......................... = 0&lt;BR /&gt;sigvec(SIGSTOP, 0x7f7e0820, 0x7f7e082c) .......................... ERR#22 EINVAL&lt;BR /&gt;sigvec(SIGTSTP, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGCONT, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGTTIN, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGTTOU, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGURG, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGLOST, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGRESERVE, 0x7f7e0820, 0x7f7e082c) ....................... ERR#22 EINVAL&lt;BR /&gt;sigvec(SIGDIL, 0x7f7e0820, 0x7f7e082c) ........................... ERR#22 EINVAL&lt;BR /&gt;sigvec(SIGXCPU, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGXFSZ, 0x7f7e0820, 0x7f7e082c) .......................... = 0&lt;BR /&gt;sigvec(SIGCANCEL, 0x7f7e0820, 0x7f7e082c) ........................ ERR#22 EINVAL&lt;BR /&gt;sigvec(SIGGFAULT, 0x7f7e0820, 0x7f7e082c) ........................ ERR#22 EINVAL&lt;BR /&gt;sigvec(SIGRT1, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT2, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT3, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT4, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT5, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT6, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT7, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;sigvec(SIGRT8, 0x7f7e0820, 0x7f7e082c) ........................... = 0&lt;BR /&gt;semget(0x1090522, 1, IPC_CREAT|IPC_EXCL|0644) .................... ERR#17 EEXIST&lt;BR /&gt;semget(0x1090522, 1, 0) .......................................... = 325&lt;BR /&gt;semctl(325, 0, GETPID, 0) ........................................ = 0&lt;BR /&gt;semget(0x1090522, 1, 0) .......................................... = 325&lt;BR /&gt;semctl(325, 0, GETPID, 0) ........................................ = 0&lt;BR /&gt;( Terminating process 7742 ("/usr/sbin/inetd -l") )</description>
      <pubDate>Tue, 26 Apr 2005 04:27:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531831#M221607</guid>
      <dc:creator>Paul Murray_4</dc:creator>
      <dc:date>2005-04-26T04:27:02Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531832#M221608</link>
      <description>Can you attach the file with all the output?&lt;BR /&gt;&lt;BR /&gt;I see that you have some problems with getting the semaphores ....</description>
      <pubDate>Tue, 26 Apr 2005 05:37:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531832#M221608</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-04-26T05:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531833#M221609</link>
      <description>Hi Alex - attached is the full tusc output as requested.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Paul.</description>
      <pubDate>Tue, 26 Apr 2005 05:40:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531833#M221609</guid>
      <dc:creator>Paul Murray_4</dc:creator>
      <dc:date>2005-04-26T05:40:33Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531834#M221610</link>
      <description>Unless it is poor wording on the part of tusc, I would not have expected to see a message about the process terminating - at least not if you were following forks in the tusc with -f.  From startup inetd will fork at least once to disconnect itself from the controlling terminal and all that.&lt;BR /&gt;&lt;BR /&gt;Might want to add the "display pid" option for tusc, and perhaps add timestamps to see where it may be spending lots of time.&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Apr 2005 10:04:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531834#M221610</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2005-04-27T10:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531835#M221611</link>
      <description>What does ipcs -sa give you?</description>
      <pubDate>Wed, 27 Apr 2005 10:37:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531835#M221611</guid>
      <dc:creator>Stephen Keane</dc:creator>
      <dc:date>2005-04-27T10:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531836#M221612</link>
      <description>Hmm, this part looks weird:&lt;BR /&gt;&lt;BR /&gt;mmap(NULL, 86016, PROT_READ|PROT_EXEC, MAP_SHARED|MAP_SHLIB, 3, 0x5000) = 0xc0222000&lt;BR /&gt;mmap(NULL, 20480, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_SHLIB, 3, 0x1a000) = 0x7f797000&lt;BR /&gt;close(3) ......................................................... = 0&lt;BR /&gt;stat("/usr/lib/libxti.2", 0x7f7e2c70) ............................ = 0&lt;BR /&gt;open("/usr/lib/libxti.2", O_RDONLY, 0) ........................... = 3&lt;BR /&gt;fstat(3, 0x7f7e2d38) ............................................. = 0&lt;BR /&gt;read(3, "0210010e0512@ \0\0\0\0\0\0\0\0\0".., 128) ............... = 128&lt;BR /&gt;lseek(3, 128, SEEK_SET) .......................................... = 128&lt;BR /&gt;read(3, "10\0\004\0\0\0( \001D bc\0\010\0".., 48) ................ = 48&lt;BR /&gt;read(3, "80\0\0\v\0\0\004\0\0\0\0", 12) .......................... = 12&lt;BR /&gt;lseek(3, 20480, SEEK_SET) ........................................ = 20480&lt;BR /&gt;read(3, "058cy 10\0\0\0a8\0\0\0p \0\0\001".., 112) ............... = 112&lt;BR /&gt;mmap(NULL, 86016, PROT_READ|PROT_EXEC, MAP_SHARED|MAP_SHLIB, 3, 0x5000) ERR#12 ENOMEM&lt;BR /&gt;close(3) ......................................................... = 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Why the first mmap call goes OK, but then, mmap with exactly the same parameters fails with ENOMEM?</description>
      <pubDate>Wed, 27 Apr 2005 10:40:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531836#M221612</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-04-27T10:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531837#M221613</link>
      <description>Paul -- I don't see a specific tie in to your problem, but you might want to check to see if you have the latest inetd patch which is PHNE_28312.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Kent M. Ostby&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Apr 2005 12:35:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531837#M221613</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2005-04-27T12:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Inetd Hanging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531838#M221614</link>
      <description>From your tusc output it seems that, on startup, inetd tries to create semaphore with key 0x01090522. In your case semaphore was already created possibly by previous inetd invocation and never cleaned up (maybe due to kill -9 on inetd process).&lt;BR /&gt;&lt;BR /&gt;You first need to clean up semaphore to allow inetd to start.&lt;BR /&gt;&lt;BR /&gt;# ipcrm -S 0x01090522&lt;BR /&gt;&lt;BR /&gt;Then you can try tusc'ing inetd again with the following flags (especially -k).&lt;BR /&gt;&lt;BR /&gt;# tusc -o /tmp/tusc.log -ccc -f -k -l -n -p -v -T%T -b 80 -r all -w all /usr/sbin/inetd -l&lt;BR /&gt;&lt;BR /&gt;Trace output will go to /tmp/tusc.log.</description>
      <pubDate>Thu, 28 Apr 2005 07:23:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/inetd-hanging/m-p/3531838#M221614</guid>
      <dc:creator>Ermin Borovac</dc:creator>
      <dc:date>2005-04-28T07:23:09Z</dc:date>
    </item>
  </channel>
</rss>

