What is the proper way to change hci’s default shell?

[Max Drown (Infor)]

Is changing shells as simple as editing /etc/passwd and changing

from

Code:

hci:!:1001:0:QDX(TM) Integration Services production mode:/home/hci:/bin/ksh

to

Code:

hci:!:1001:0:QDX(TM) Integration Services production mode:/home/hci:/bin/tcsh

?

Are there any side effects, gotchas?

-- Max Drown (Infor)

Topic

[John Hamilton]

Yes pretty much that simple.  hcisupt1 use tcsh as well. I done a little with it but perfer ksh my self. But it should work with little to no problem.

[Max Drown (Infor)]

This is a noobish question I know, but will the change to tcsh effect any of the Cloverleaf scripts or cron scripts?

-- Max Drown (Infor)

[John Hamilton]

Properly written scripts tell the system what shell they are to be run under in the first line of the script. If that is set correctly then you should have no problems.

[Michael Hertel]

Someone with more experience with this should clarify for me but…

ksh runs .profile

tcsh runs .cshrc

-mh

[Charlie Bursell]

Max:

Go to /home/hcispt, it uses tcsh.  You can see how it’s profiles are set up.  As a matter of fact you could copy some of the profiles, .cshrc etc. and then modify to suit your needs.

I know of no Cloverleaf routines that care which shell you are using.  As Jonathan said, when executing a script, you can use any shell you wish simply by the first line, e.g.,

     #!/usr/bin/ksh

Unless you really know what you are doing I would run the scripts using sh or ksh.  The scripting language for the csh or tcsh is vastly different.

[Max Drown (Infor)]

Thanks. I’ll check into it.

(can’t stand not having tab completion)

-- Max Drown (Infor)

[John Hamilton]

The first line of any script tells the it what shell to run that script to run under.

And Charlie wrong John.  Pass Christian is almost back to normal after Katrina.

[Richard Hart]

FWIW.

We use multiple users to control Cloverleaf, all within the Unix group ‘hcimgr’.

We use ‘hci’ as an ‘admin’ user and this owns the Cloverleaf installation and our ‘admin’ code.

User ‘hcimgr’ is the ‘manager’ all the test and prod Cloverleaf sites.

Users ‘hexxxxx’ are our personal logins where we perform development work.

We use ‘sudo’ from our personal logins (or from operations) to login as hci or hcimgr.

With this setup, ‘hci’ and the Cloverleaf installation is pretty much vanilla.

We can also protect code by having this owned by ‘hci’ within a site owned by ‘hcimgr’ – we actually use link links as we share code across multiple sites.

[Max Drown (Infor)]

Richard Hart wrote:

FWIW.

We use multiple users to control Cloverleaf, all within the Unix group ‘hcimgr’.

We use ‘hci’ as an ‘admin’ user and this owns the Cloverleaf installation and our ‘admin’ code.

User ‘hcimgr’ is the ‘manager’ all the test and prod Cloverleaf sites.

Users ‘hexxxxx’ are our personal logins where we perform development work.

We use ‘sudo’ from our personal logins (or from operations) to login as hci or hcimgr.

With this setup, ‘hci’ and the Cloverleaf installation is pretty much vanilla.

We can also protect code by having this owned by ‘hci’ within a site owned by ‘hcimgr’ – we actually use link links as we share code across multiple sites.

Do you su to hci to turn on/off processes? Or how do you handle that?

-- Max Drown (Infor)

[Author]

Replies