<?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: csh and ksh shells in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896728#M96559</link>
    <description>Hi Shiv:&lt;BR /&gt;&lt;BR /&gt;It doesn't matter that a startup script written in one shell language starts another script written in another language.&lt;BR /&gt;&lt;BR /&gt;What matters is that the interpreter declared on the "she-bang" line --- the first line of a script that begins with "#!" --- matches the command syntax in the body of the script.&lt;BR /&gt;&lt;BR /&gt;That is, if you write:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/csh&lt;BR /&gt;&lt;BR /&gt;...then the syntax used afterwards is C-shell.&lt;BR /&gt;&lt;BR /&gt;That does *not* prevent you from launching another script that is written in the Korn or Posix shell, however.  For instance:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/csh&lt;BR /&gt;...&lt;BR /&gt;/usr/local/bin/mything&lt;BR /&gt;&lt;BR /&gt;...where '/usr/local/bin/mything' is a Korn shell script.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sun, 12 Nov 2006 16:12:38 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2006-11-12T16:12:38Z</dc:date>
    <item>
      <title>csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896727#M96558</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Our one of the weblogic server startup script is configured to start as a user whose environement shell varibale&lt;BR /&gt;is setup in csh ( c shell ).&lt;BR /&gt;&lt;BR /&gt;If i start the weblogic start up script changing the shell in ksh korn shell; will it cause any issue ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv</description>
      <pubDate>Sun, 12 Nov 2006 15:42:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896727#M96558</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2006-11-12T15:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896728#M96559</link>
      <description>Hi Shiv:&lt;BR /&gt;&lt;BR /&gt;It doesn't matter that a startup script written in one shell language starts another script written in another language.&lt;BR /&gt;&lt;BR /&gt;What matters is that the interpreter declared on the "she-bang" line --- the first line of a script that begins with "#!" --- matches the command syntax in the body of the script.&lt;BR /&gt;&lt;BR /&gt;That is, if you write:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/csh&lt;BR /&gt;&lt;BR /&gt;...then the syntax used afterwards is C-shell.&lt;BR /&gt;&lt;BR /&gt;That does *not* prevent you from launching another script that is written in the Korn or Posix shell, however.  For instance:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/csh&lt;BR /&gt;...&lt;BR /&gt;/usr/local/bin/mything&lt;BR /&gt;&lt;BR /&gt;...where '/usr/local/bin/mything' is a Korn shell script.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 12 Nov 2006 16:12:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896728#M96559</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-11-12T16:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896729#M96560</link>
      <description>Hi, the varibales are defined differently in csh and ksh:&lt;BR /&gt; ksh "export DISPLAY=xxx.xxx.xxx.xxx:0.0"&lt;BR /&gt; ksh "export PATH=$PATH"&lt;BR /&gt; csh "set display=xxx.xxx.xxx.xxx:0.0"&lt;BR /&gt; csh "set path=( $path )"&lt;BR /&gt;&lt;BR /&gt;You have to checl and maybe modify that script if you want to use ksh.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Yang</description>
      <pubDate>Sun, 12 Nov 2006 16:20:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896729#M96560</guid>
      <dc:creator>Yang Qin_1</dc:creator>
      <dc:date>2006-11-12T16:20:54Z</dc:date>
    </item>
    <item>
      <title>Re: csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896730#M96561</link>
      <description>The script being run by a weblogic applicaton user to start weblogic servers is in c shell. i use powerbroker to become that user to start the server.&lt;BR /&gt;&lt;BR /&gt;once i become that particular user which uses c shell; i am not able to use "$set -o vi" which i usually use to access previous commands.&lt;BR /&gt;&lt;BR /&gt;i usually use ksh shell to access previous commands by executing $set -o vi.&lt;BR /&gt;&lt;BR /&gt;just wanted to know if i execute ksh and then run the startup script.. will it impact anything ?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Shiv&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 12 Nov 2006 16:32:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896730#M96561</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2006-11-12T16:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896731#M96562</link>
      <description>If you want to run a c shell script under k shell, you have to test it. Depends on what is written in that script, it may work or it may fail.&lt;BR /&gt;&lt;BR /&gt;If you just want to have commands history under csh. You can try "history", it will list the commands you have typed. "!2" will excute the command you have run the one befire last command. Read manpage of csh to have more information on command history.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Yang</description>
      <pubDate>Sun, 12 Nov 2006 17:10:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896731#M96562</guid>
      <dc:creator>Yang Qin_1</dc:creator>
      <dc:date>2006-11-12T17:10:27Z</dc:date>
    </item>
    <item>
      <title>Re: csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896732#M96563</link>
      <description>Hi (again) Shiv:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; You wrote, "once i become that particular user which uses c shell; i am not able to use "$set -o vi" which i usually use to access previous commands."&lt;BR /&gt;&lt;BR /&gt;That's true.  The retrieval of the shell history of commands using 'vi' is a Posix/Korn method; not a C-shell ('csh') one.&lt;BR /&gt;&lt;BR /&gt;However, once you are in the 'csh' you can switch to 'ksh' or 'sh' by typing the name of the shell in which you want to operate:&lt;BR /&gt;&lt;BR /&gt;# ksh&lt;BR /&gt;&lt;BR /&gt;This starts a new shell, and the environmental variables you had before will need to be reestablished.  When you exit this shell, you will return to the predecesor.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; You also asked: "just wanted to know if i execute ksh and then run the startup script.. will it impact anything?"&lt;BR /&gt;&lt;BR /&gt;No, you will not, as I first responded.  You can start any binary or script of any kind from any shell type.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 12 Nov 2006 17:32:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896732#M96563</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-11-12T17:32:56Z</dc:date>
    </item>
    <item>
      <title>Re: csh and ksh shells</title>
      <link>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896733#M96564</link>
      <description>Hi Shiv:&lt;BR /&gt;&lt;BR /&gt;Ooops, I meant to write:&lt;BR /&gt;&lt;BR /&gt;This starts a new shell, and the environmental variables you had before will not need to be reestablished."&lt;BR /&gt;&lt;BR /&gt;Consider:&lt;BR /&gt;&lt;BR /&gt;# echo "I am a ${SHELL} shell"&lt;BR /&gt;I am a /sbin/sh shell&lt;BR /&gt;# export X=shiv&lt;BR /&gt;# export Y=jrf&lt;BR /&gt;# csh&lt;BR /&gt;# echo "I am the ${shell}"&lt;BR /&gt;I am the /usr/bin/csh&lt;BR /&gt;# echo "${X} asked a question and ${Y} answered"&lt;BR /&gt;shiv asked a question and jrf answered&lt;BR /&gt;# set Z=ok&lt;BR /&gt;# echo ${Z}&lt;BR /&gt;ok!&lt;BR /&gt;# exit #...going back to original shell!&lt;BR /&gt;# echo ${Z}&lt;BR /&gt;sh: Z: Parameter not set.&lt;BR /&gt;&lt;BR /&gt;...The last echo of ${Z} shows that the parent does not inherit the child's environment.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF... &lt;BR /&gt;</description>
      <pubDate>Sun, 12 Nov 2006 17:54:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/csh-and-ksh-shells/m-p/3896733#M96564</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-11-12T17:54:12Z</dc:date>
    </item>
  </channel>
</rss>

