"toor" account

After I enable the "toor" account, and logon as "toor", I notice that there is no shell set when I type env.

I type env and receive the following:

Code:
SHELL=

If I type echo $SHELL, it returns nothing but the prompt. It acts like there is no shell set.

What shell am I actually using after I enable the "toor" account and logon as "toor"?
 
Niatross said:
After I enable the "toor" account, and logon as "toor", I notice that there is no shell set when I type env.

I type env and receive the following:

Code:
SHELL=

If I type echo $SHELL, it returns nothing but the prompt. It acts like there is no shell set.

What shell am I actually using after I enable the "toor" account and logon as "toor"?

The default shell is /bin/sh. The toor account is intended to provide an alternative to the root account for setting your favoured shell (this is not recommended forroot).
 
I understand the default shell is /bin/sh, but I'll repeat my question again.

I type env and receive the following:

Code:
SHELL=

I type echo $SHELL and receive a null value (AKA: nothing.....nada).

Why isn't env returning "SHELL=/bin/sh"?

Why isn't echo $SHELL returning "/bin/sh"?

I'll tell you what...do it yourself.
  1. Enable the toor account (ex: passwd toor).
  2. Logout and login as "toor".
  3. Type env and tell me what value you get under "SHELL="
  4. Type echo $SHELL and tell me what you get.
 
Pretty sure that's just the way /bin/sh works.

For example, if you login using any other shell, then manually run /bin/sh, none of the SHELL env vars are changed. They still point to your previous shell.
 
Back
Top