<?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: no .sh_history file in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754892#M22300</link>
    <description>Shalom joseph,&lt;BR /&gt;&lt;BR /&gt;This is a Linux system.&lt;BR /&gt;&lt;BR /&gt;It does not use the .sh_history file.&lt;BR /&gt;&lt;BR /&gt;Take a look at $HOME/.bash_history&lt;BR /&gt;&lt;BR /&gt;You will see what you would expect in .sh_history&lt;BR /&gt;&lt;BR /&gt;You CAN have .sh_history if you want, but most Linux admins (like me) will if they touch the system look for a .bash_history file.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 20 Mar 2006 11:39:09 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-03-20T11:39:09Z</dc:date>
    <item>
      <title>no .sh_history file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754889#M22297</link>
      <description>I'm running RHEL AS3.  My users are set up to use /bin/ksh.  However, there is no .sh_history being created for any of them of the users.  Nothing is setup in either the /etc/profile or the respective /home/&lt;USER&gt;/.profile which is creating the file somewhere else.  If I issue "history" as a user, it will display command history for current session.  My question is: "WHY ISN'T A .sh_history FILE CREATED"?????  Shouldn't that happen by default?  Please respond if you can address the PROBLEM.  No work around recommendations please!!!!  thx.&lt;/USER&gt;</description>
      <pubDate>Mon, 20 Mar 2006 11:27:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754889#M22297</guid>
      <dc:creator>joseph wholey</dc:creator>
      <dc:date>2006-03-20T11:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: no .sh_history file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754890#M22298</link>
      <description>For ksh, HISTFILE should be defined. If it's not, no history file is used. See ksh man page. Put the following in /etc/profile:&lt;BR /&gt;&lt;BR /&gt;HISTFILE=${HOME}/.sh_history</description>
      <pubDate>Mon, 20 Mar 2006 11:30:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754890#M22298</guid>
      <dc:creator>Jeff_Traigle</dc:creator>
      <dc:date>2006-03-20T11:30:53Z</dc:date>
    </item>
    <item>
      <title>Re: no .sh_history file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754891#M22299</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Your korn shell uses a deafult buffer for the last commands. If you would like to setup a history file, you will need to add this to your .profile or /etc/profile.&lt;BR /&gt;&lt;BR /&gt;EDITOR=vi&lt;BR /&gt;HISTFILE=${HOME}/.sh_history_`who am i|awk '{ print $1}'`&lt;BR /&gt;HISTSIZE=1000&lt;BR /&gt;export EDITOR HISTFILE HISTSIZE&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Mon, 20 Mar 2006 11:32:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754891#M22299</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-20T11:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: no .sh_history file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754892#M22300</link>
      <description>Shalom joseph,&lt;BR /&gt;&lt;BR /&gt;This is a Linux system.&lt;BR /&gt;&lt;BR /&gt;It does not use the .sh_history file.&lt;BR /&gt;&lt;BR /&gt;Take a look at $HOME/.bash_history&lt;BR /&gt;&lt;BR /&gt;You will see what you would expect in .sh_history&lt;BR /&gt;&lt;BR /&gt;You CAN have .sh_history if you want, but most Linux admins (like me) will if they touch the system look for a .bash_history file.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 20 Mar 2006 11:39:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754892#M22300</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-20T11:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: no .sh_history file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754893#M22301</link>
      <description>Similar discussion from last week:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1003728" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1003728&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Mon, 20 Mar 2006 11:44:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754893#M22301</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2006-03-20T11:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: no .sh_history file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754894#M22302</link>
      <description>Sorry... I'm using /bin/ksh as my default shell.  I was under the impression (actually I believe I read it somewhere) that by default .sh_history will be created.  On all of my AIX machines, I do not define .sh_history in my .profile or in /etc/profile, however, it does get created.  Please advise. thx.</description>
      <pubDate>Mon, 20 Mar 2006 12:20:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/no-sh-history-file/m-p/3754894#M22302</guid>
      <dc:creator>joseph wholey</dc:creator>
      <dc:date>2006-03-20T12:20:38Z</dc:date>
    </item>
  </channel>
</rss>

