Very Computer

It was there in SunOS 4.1.3 and now appears to be gone in SunOS 5.X (e.g.
Solaris 2.4).  Is there an equivilant or can the the S.A. change a user's
default shell?

--
Dan Gold

TRW ASG Sunnyvale

I usually do this by editing the users default shell in
/etc/passwd.

Caution:  You should always do the following when
manually editing passwd, shadow and group files.

0)  Copy passwd or shadow as appropriate b/4 changing.
1)  Always keep logged in as root.
2)  Telnet back to yourself.
3)  Login as a standard user.
4)  su -

If the su - fails replace defective with copy in
root shell.

: I usually do this by editing the users default shell in
: /etc/passwd.

wrong !!!
as long as you don't use NIS(+)
you should use usermod
man usermod for more details.

                Marcin;)
--
------------------------------------------------------------------------------

..it's de facto >>--| http://www.pk.edu.pl:8001/ |-->> 2 line only sig....
------------------------------------------------------------------------------

 >I usually do this by editing the users default shell in
 >/etc/passwd.

 >Caution:  You should always do the following when
 >manually editing passwd, shadow and group files.

 >0)  Copy passwd or shadow as appropriate b/4 changing.
 >1)  Always keep logged in as root.
 >2)  Telnet back to yourself.
 >3)  Login as a standard user.
 >4)  su -

 >If the su - fails replace defective with copy in
 >root shell.

man usermod

Only executable by root.

--
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)810-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______

  Web admin:  chimera,nn,tin,jove,kermit - free's best!/________/ /  /  / /

No need for any fancy programs. Just have the SA give everybody /bin/sh.
Each person can then use whatever shell by setting the SHELL environment
variable in the .profile.

SHELL=/bin/ksh
export SHELL
exec $SHELL

All X apps (xterm, cmdtool, etc.) will check the SHELL variable for your
prefered shell.

-David

|> Each person can then use whatever shell by setting the SHELL environment
|> variable in the .profile.
|>
|> SHELL=/bin/ksh
|> export SHELL
|> exec $SHELL

But what about access that doesn't pass through a login stage?  Access via
"rsh" is fairly common and .profile isn't read then if your shell in
/etc/passwd is /bin/sh.