<?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: System command Logging in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004442#M425133</link>
    <description>Hi Gene,&lt;BR /&gt;&lt;BR /&gt;1.  The 'history' built-in will show you the last 15 commands.  This command history is stored in $HISTFILE, which is set to ~/.sh_history, by default.  As long as $HISTFILE is set, and $HISTSIZE is not 0, command history will be recorded.&lt;BR /&gt;&lt;BR /&gt;2.  # uptime&lt;BR /&gt;&lt;BR /&gt;PCS</description>
    <pubDate>Wed, 20 Sep 2006 11:25:15 GMT</pubDate>
    <dc:creator>spex</dc:creator>
    <dc:date>2006-09-20T11:25:15Z</dc:date>
    <item>
      <title>System command Logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004439#M425130</link>
      <description>Is it possible to log the commands a user types in at either the console or a telnet session? I ask because I want to see if someone, or hell maybe even me, issued an hpvmstop command to shut off our virtual machines. I came in today and they were all stopped.&lt;BR /&gt;Is this possible?&lt;BR /&gt;&lt;BR /&gt;Also, how can I get the "Uptime" of the HP-UX server just in case it ASR'd? OS is HP-UX 11i v2 on an rx2620.</description>
      <pubDate>Wed, 20 Sep 2006 11:06:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004439#M425130</guid>
      <dc:creator>Gene Laoyan</dc:creator>
      <dc:date>2006-09-20T11:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: System command Logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004440#M425131</link>
      <description>&lt;!--!*#--&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;i think you can use script(1) for record a session user, you could put it in the user profile for automatic launch (never tested).&lt;BR /&gt;&lt;BR /&gt;good luck</description>
      <pubDate>Wed, 20 Sep 2006 11:22:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004440#M425131</guid>
      <dc:creator>mobidyc</dc:creator>
      <dc:date>2006-09-20T11:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: System command Logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004441#M425132</link>
      <description>Gene,&lt;BR /&gt;&lt;BR /&gt;I would check the history file to see if the command is listed there. It won't tell you who did it, but we asume it was somebody with root privileges.&lt;BR /&gt;&lt;BR /&gt;Also if you need to track those type of things down, I would convert to a trusted system or install sudo in the machine, to give priviledges to what users can execute or even check what user what the one that exected a certain command in the future.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jaime.</description>
      <pubDate>Wed, 20 Sep 2006 11:23:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004441#M425132</guid>
      <dc:creator>Jaime Bolanos Rojas.</dc:creator>
      <dc:date>2006-09-20T11:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: System command Logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004442#M425133</link>
      <description>Hi Gene,&lt;BR /&gt;&lt;BR /&gt;1.  The 'history' built-in will show you the last 15 commands.  This command history is stored in $HISTFILE, which is set to ~/.sh_history, by default.  As long as $HISTFILE is set, and $HISTSIZE is not 0, command history will be recorded.&lt;BR /&gt;&lt;BR /&gt;2.  # uptime&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Wed, 20 Sep 2006 11:25:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004442#M425133</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-09-20T11:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: System command Logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004443#M425134</link>
      <description>script solution can easily be circumvented by writing over the log file byu the user issuing the questionable commands. So, even though it is a way, it does not give you the untampered logs you may want to see, right after a suspicious diappearance of a critical file.&lt;BR /&gt;&lt;BR /&gt;check powerbroker from symark (&lt;A href="http://symark.com)" target="_blank"&gt;http://symark.com)&lt;/A&gt; It has capability of logging commands to a remote server (where you keep eternal users away from). It is not free. Actually it may be quite costly for a casual logging. But at the same time, it gives you the ability to show untampered logs to the Sarbanes-Oxymoron auditors. It makes them so happy, you can not imagine :)</description>
      <pubDate>Wed, 20 Sep 2006 11:42:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004443#M425134</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2006-09-20T11:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: System command Logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004444#M425135</link>
      <description>Thanks everyone!</description>
      <pubDate>Wed, 20 Sep 2006 11:47:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-command-logging/m-p/5004444#M425135</guid>
      <dc:creator>Gene Laoyan</dc:creator>
      <dc:date>2006-09-20T11:47:34Z</dc:date>
    </item>
  </channel>
</rss>

