<?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: access log in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444445#M207788</link>
    <description>In that case, "inetd -l" is your boy. You can try this out by issueing an "inetd -l" command to a running session. This has the effect of toggling logging on or off each time it is used.&lt;BR /&gt;</description>
    <pubDate>Wed, 15 Dec 2004 12:25:22 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2004-12-15T12:25:22Z</dc:date>
    <item>
      <title>access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444440#M207783</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I try to find a way to configure /etc/syslog.conf to elaborate a log of user connection on my HPUX 11i server.&lt;BR /&gt;&lt;BR /&gt;Am I in a wrong way with /etc/syslog.conf?&lt;BR /&gt;&lt;BR /&gt;Is there any other existing logfile that already do that?&lt;BR /&gt;&lt;BR /&gt;Or is there any script I could make to do that?&lt;BR /&gt;&lt;BR /&gt;Pls help... Thx&lt;BR /&gt;&lt;BR /&gt;Stf ;-)</description>
      <pubDate>Wed, 15 Dec 2004 11:51:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444440#M207783</guid>
      <dc:creator>Stf</dc:creator>
      <dc:date>2004-12-15T11:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444441#M207784</link>
      <description>What about "last" command ?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Fred&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Dec 2004 11:55:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444441#M207784</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2004-12-15T11:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444442#M207785</link>
      <description>You can alter the inetd setup to add -l (logging) but you are going to see a ton of data. Man inetd for details.&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Dec 2004 11:58:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444442#M207785</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-12-15T11:58:54Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444443#M207786</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You can take a look at tcp_wrapper,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcp_wrappers-7.6/" target="_blank"&gt;http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/tcp_wrappers-7.6/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Dec 2004 12:07:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444443#M207786</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2004-12-15T12:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444444#M207787</link>
      <description>your solutions looks good, but in fact my customer really want to do that by configuring /etc/syslog.conf to generate a logfile of connection tentative (good or bad.&lt;BR /&gt;He wants to know :&lt;BR /&gt;user / IP_adress / connection success or not / and if it's telnet or ftp etc...&lt;BR /&gt;&lt;BR /&gt;Stf&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Dec 2004 12:15:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444444#M207787</guid>
      <dc:creator>Stf</dc:creator>
      <dc:date>2004-12-15T12:15:39Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444445#M207788</link>
      <description>In that case, "inetd -l" is your boy. You can try this out by issueing an "inetd -l" command to a running session. This has the effect of toggling logging on or off each time it is used.&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Dec 2004 12:25:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444445#M207788</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-12-15T12:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444446#M207789</link>
      <description>Hi Stf:&lt;BR /&gt;  you can "last -R" command for succesfull logins and "lastb -R" for unsuccesfull logins. Both commands display the information you need.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;/Claudio</description>
      <pubDate>Thu, 16 Dec 2004 11:26:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444446#M207789</guid>
      <dc:creator>Claudio Martin_1</dc:creator>
      <dc:date>2004-12-16T11:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444447#M207790</link>
      <description>OK I tried tcp_wrappers but I have funny questions...:&lt;BR /&gt;&lt;BR /&gt;where are the logs to monitor tcp connections?&lt;BR /&gt;&lt;BR /&gt;how does tcp_wrappers works?&lt;BR /&gt;&lt;BR /&gt;thx&lt;BR /&gt;&lt;BR /&gt;Stf ;-)</description>
      <pubDate>Wed, 29 Dec 2004 04:33:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444447#M207790</guid>
      <dc:creator>Stf</dc:creator>
      <dc:date>2004-12-29T04:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: access log</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444448#M207791</link>
      <description>Hi Stf&lt;BR /&gt;&lt;BR /&gt;Just my idea....&lt;BR /&gt;Have you ever heard about eTrust software (This call : Access Control)?&lt;BR /&gt;It is a complete monitor and access tool for every Unix system.&lt;BR /&gt;But you have to buy it....&lt;BR /&gt;:) :)&lt;BR /&gt;&lt;BR /&gt;Best and regard,&lt;BR /&gt;-HAPY NEW YEAR-&lt;BR /&gt;HoangChiCong</description>
      <pubDate>Wed, 29 Dec 2004 05:00:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/access-log/m-p/3444448#M207791</guid>
      <dc:creator>Hoang Chi Cong_1</dc:creator>
      <dc:date>2004-12-29T05:00:29Z</dc:date>
    </item>
  </channel>
</rss>

