<?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: how to trace a command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156626#M158576</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;is that for future purposes or for this incident?&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
    <pubDate>Mon, 05 Jan 2004 16:21:07 GMT</pubDate>
    <dc:creator>Michael Schulte zur Sur</dc:creator>
    <dc:date>2004-01-05T16:21:07Z</dc:date>
    <item>
      <title>how to trace a command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156624#M158574</link>
      <description>one of unix users deleted one directory.&lt;BR /&gt;Unfortunately, the user doesn't have ~/.sh_history file so that I can not trace who deleted the directory.&lt;BR /&gt;&lt;BR /&gt;Does anyone know how to trace a command run by a specific user ?</description>
      <pubDate>Mon, 05 Jan 2004 16:13:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156624#M158574</guid>
      <dc:creator>Brian Lee_4</dc:creator>
      <dc:date>2004-01-05T16:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: how to trace a command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156625#M158575</link>
      <description>Unless the user has a .sh_history or equivalent, (depending on the type of shell) the answer is no, unless you run system auditing, which is probably unlikely.</description>
      <pubDate>Mon, 05 Jan 2004 16:18:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156625#M158575</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2004-01-05T16:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: how to trace a command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156626#M158576</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;is that for future purposes or for this incident?&lt;BR /&gt;&lt;BR /&gt;greetings,&lt;BR /&gt;&lt;BR /&gt;Michael&lt;BR /&gt;</description>
      <pubDate>Mon, 05 Jan 2004 16:21:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156626#M158576</guid>
      <dc:creator>Michael Schulte zur Sur</dc:creator>
      <dc:date>2004-01-05T16:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: how to trace a command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156627#M158577</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You cannot trace a command unless it is stored in the history. Had this been a system related command, you could have tried syslog.log where it logs some systems command.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds</description>
      <pubDate>Mon, 05 Jan 2004 16:22:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-trace-a-command/m-p/3156627#M158577</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2004-01-05T16:22:34Z</dc:date>
    </item>
  </channel>
</rss>

