<?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: log file for services in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044990#M135149</link>
    <description>In a nutshell, if a service is defined in /etc/inetd.conf and /etc/services, it will not be started by the inetd daemon until it is needed.  You will never see an FTP process on your system unless someone is actively doing an FTP to your system.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 08 Aug 2003 12:17:32 GMT</pubDate>
    <dc:creator>Patrick Wallek</dc:creator>
    <dc:date>2003-08-08T12:17:32Z</dc:date>
    <item>
      <title>log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044981#M135140</link>
      <description>When the services in /etc/inetd.conf start at boot up, is information about these services logged anywhere? if so, where would I find it?&lt;BR /&gt;&lt;BR /&gt;Ron</description>
      <pubDate>Fri, 08 Aug 2003 11:53:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044981#M135140</guid>
      <dc:creator>Ron Bromwell</dc:creator>
      <dc:date>2003-08-08T11:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044982#M135141</link>
      <description>Hi,&lt;BR /&gt;you find all the information in /var/adm/syslog/sysglog.log&lt;BR /&gt;&lt;BR /&gt;do a&lt;BR /&gt;&lt;BR /&gt;grep inet  /var/adm/syslog/sysglog.log&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;and search for "Added Service"&lt;BR /&gt;&lt;BR /&gt;   Massimo&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2003 12:02:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044982#M135141</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-08-08T12:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044983#M135142</link>
      <description>From the man pages.&lt;BR /&gt;&lt;BR /&gt; In such&lt;BR /&gt;      cases, inetd refuses the connection from the same service invocation&lt;BR /&gt;      five times.  This is visible in the system log if inetd connection&lt;BR /&gt;      logging and syslogd logging for the daemon facility are both enabled&lt;BR /&gt;      (see syslogd(1M)).                                                 &lt;BR /&gt;  -l   By default, inetd starts with connection logging disabled.&lt;BR /&gt;                If no inetd is running, the -l option causes the inetd to&lt;BR /&gt;                start with connection logging enabled.  Otherwise the -l&lt;BR /&gt;                option causes inetd to send the signal SIGQUIT to the inetd&lt;BR /&gt;                that is already running, which causes it to toggle the state&lt;BR /&gt;                of connection logging.</description>
      <pubDate>Fri, 08 Aug 2003 12:04:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044983#M135142</guid>
      <dc:creator>Ken Hubnik_2</dc:creator>
      <dc:date>2003-08-08T12:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044984#M135143</link>
      <description>Yes it is logged in /var/adm/syslog/syslog.log.&lt;BR /&gt;&lt;BR /&gt;And it looks like this&lt;BR /&gt;&lt;BR /&gt;....&lt;BR /&gt;Jun  3 15:35:26 polonium inetd[1353]: shell/tcp: Added service, server /usr/lbin&lt;BR /&gt;/remshd&lt;BR /&gt;Jun  3 15:35:26 polonium inetd[1353]: spc/tcp: Added service, server /usr/bms/bi&lt;BR /&gt;n/softspcd&lt;BR /&gt;Jun  3 15:35:26 polonium inetd[1353]: telnet/tcp: Added service, server /usr/lbi&lt;BR /&gt;n/telnetd&lt;BR /&gt;Jun  3 15:35:26 polonium inetd[1353]: time/udp: Added service, server internal&lt;BR /&gt;Jun  3 15:35:26 polonium inetd[1353]: time/tcp: Added service, server internal&lt;BR /&gt;Jun  3 15:35:26 polonium inetd[1353]: rpc.cmsd/udp: Added service, server /usr/d&lt;BR /&gt;....&lt;BR /&gt;&lt;BR /&gt;look at the beginning of syslog.log&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Roland</description>
      <pubDate>Fri, 08 Aug 2003 12:06:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044984#M135143</guid>
      <dc:creator>RolandH</dc:creator>
      <dc:date>2003-08-08T12:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044985#M135144</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;by default services of /etc/inetd.conf logs store in /var/adm/syslog/syslog.log file&lt;BR /&gt;&lt;BR /&gt;for all the services trace the log u have to enable the logging service inetd daemon using command &lt;BR /&gt;&lt;BR /&gt;inetd -l &lt;BR /&gt;&lt;BR /&gt;it will enable the logging service&lt;BR /&gt;&lt;BR /&gt;Thanx</description>
      <pubDate>Fri, 08 Aug 2003 12:07:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044985#M135144</guid>
      <dc:creator>Suresh Patoria</dc:creator>
      <dc:date>2003-08-08T12:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044986#M135145</link>
      <description>the log shows the services as added, but when i preform a ps -ef and grep on the service it does not show up. Is there someplace else I could look.</description>
      <pubDate>Fri, 08 Aug 2003 12:07:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044986#M135145</guid>
      <dc:creator>Ron Bromwell</dc:creator>
      <dc:date>2003-08-08T12:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044987#M135146</link>
      <description>Rom,&lt;BR /&gt;&lt;BR /&gt;INETD is your "super-daemon" that controls startup of "server" programs on a UNIX host's end. Along with /etc/services - it serves as a director which "service" needs to be launched based on the properties of the connection -- ie. tcp or udp.. and the port number. &lt;BR /&gt;&lt;BR /&gt;If you want explicit logging of when these listed services in /etc/inetd are called and from where -- you can use TCP wrappers (or the tcpd) program. By the use of "tcp wrappers" you can log and control who has acccess to which services and makes your system a little bit secure... Most newer inetd programs already incorporate the features of tcp wrappers.&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2003 12:13:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044987#M135146</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2003-08-08T12:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044988#M135147</link>
      <description>Hi ron,&lt;BR /&gt;&lt;BR /&gt;the service will start if you need it. So start a telnet session to your system and then grep for telnetd.&lt;BR /&gt;Ot start a ftp session to your system and then grep for the ftpd. You will see it is running.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Roland</description>
      <pubDate>Fri, 08 Aug 2003 12:15:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044988#M135147</guid>
      <dc:creator>RolandH</dc:creator>
      <dc:date>2003-08-08T12:15:13Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044989#M135148</link>
      <description>And by the way Rom, you will not be able to "see" via ps|grep ALL the services as these "services" will only be active when there is a connection to them .. ie. telnetd, ftpd, etc...&lt;BR /&gt;&lt;BR /&gt;If you install TCP wrappers and explicit logging (you may tweak your syslog.conf so you control system logging...) - you may monitor inetd connections by doing a:&lt;BR /&gt;&lt;BR /&gt;telnet &lt;YOURHOST&gt; &lt;PORT number=""&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/PORT&gt;&lt;/YOURHOST&gt;</description>
      <pubDate>Fri, 08 Aug 2003 12:17:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044989#M135148</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2003-08-08T12:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: log file for services</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044990#M135149</link>
      <description>In a nutshell, if a service is defined in /etc/inetd.conf and /etc/services, it will not be started by the inetd daemon until it is needed.  You will never see an FTP process on your system unless someone is actively doing an FTP to your system.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2003 12:17:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/log-file-for-services/m-p/3044990#M135149</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2003-08-08T12:17:32Z</dc:date>
    </item>
  </channel>
</rss>

