Why login with user created with useradd command in Debian has no enviroment set? [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I started to learn linux and I came a cross problem I would like to ask. After I use useradd command in debian, I get new user with home directory. I check that directories from /etc/skel are copied and everything seems fine. But when I log to user with su - user I get only $ sign and I see that PS1 variable is not set, colours and other things. User created with adduser doesn't have this problem and If I check difference between .bashrc and .profile files for both users, there are the same. So why is this happening?
debian users environment-variables
closed as off-topic by Jeff Schaller, G-Man, SatÃ
 Katsura, Rui F Ribeiro, GAD3R Feb 17 at 17:21
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, G-Man, Satà  Katsura, Rui F Ribeiro, GAD3R
add a comment |Â
up vote
0
down vote
favorite
I started to learn linux and I came a cross problem I would like to ask. After I use useradd command in debian, I get new user with home directory. I check that directories from /etc/skel are copied and everything seems fine. But when I log to user with su - user I get only $ sign and I see that PS1 variable is not set, colours and other things. User created with adduser doesn't have this problem and If I check difference between .bashrc and .profile files for both users, there are the same. So why is this happening?
debian users environment-variables
closed as off-topic by Jeff Schaller, G-Man, SatÃ
 Katsura, Rui F Ribeiro, GAD3R Feb 17 at 17:21
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, G-Man, Satà  Katsura, Rui F Ribeiro, GAD3R
2
Are you certain that you used the hyphen in thesu - user
?
â Jeff Schaller
Feb 16 at 20:05
1
Relating: unix.stackexchange.com/q/121071/117549
â Jeff Schaller
Feb 16 at 20:06
1
Which login shell was assigned to the user?
â steeldriver
Feb 16 at 20:19
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I started to learn linux and I came a cross problem I would like to ask. After I use useradd command in debian, I get new user with home directory. I check that directories from /etc/skel are copied and everything seems fine. But when I log to user with su - user I get only $ sign and I see that PS1 variable is not set, colours and other things. User created with adduser doesn't have this problem and If I check difference between .bashrc and .profile files for both users, there are the same. So why is this happening?
debian users environment-variables
I started to learn linux and I came a cross problem I would like to ask. After I use useradd command in debian, I get new user with home directory. I check that directories from /etc/skel are copied and everything seems fine. But when I log to user with su - user I get only $ sign and I see that PS1 variable is not set, colours and other things. User created with adduser doesn't have this problem and If I check difference between .bashrc and .profile files for both users, there are the same. So why is this happening?
debian users environment-variables
edited Feb 16 at 20:03
Jeff Schaller
31.2k846105
31.2k846105
asked Feb 16 at 19:57
user276387
1
1
closed as off-topic by Jeff Schaller, G-Man, SatÃ
 Katsura, Rui F Ribeiro, GAD3R Feb 17 at 17:21
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, G-Man, Satà  Katsura, Rui F Ribeiro, GAD3R
closed as off-topic by Jeff Schaller, G-Man, SatÃ
 Katsura, Rui F Ribeiro, GAD3R Feb 17 at 17:21
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â Jeff Schaller, G-Man, Satà  Katsura, Rui F Ribeiro, GAD3R
2
Are you certain that you used the hyphen in thesu - user
?
â Jeff Schaller
Feb 16 at 20:05
1
Relating: unix.stackexchange.com/q/121071/117549
â Jeff Schaller
Feb 16 at 20:06
1
Which login shell was assigned to the user?
â steeldriver
Feb 16 at 20:19
add a comment |Â
2
Are you certain that you used the hyphen in thesu - user
?
â Jeff Schaller
Feb 16 at 20:05
1
Relating: unix.stackexchange.com/q/121071/117549
â Jeff Schaller
Feb 16 at 20:06
1
Which login shell was assigned to the user?
â steeldriver
Feb 16 at 20:19
2
2
Are you certain that you used the hyphen in the
su - user
?â Jeff Schaller
Feb 16 at 20:05
Are you certain that you used the hyphen in the
su - user
?â Jeff Schaller
Feb 16 at 20:05
1
1
Relating: unix.stackexchange.com/q/121071/117549
â Jeff Schaller
Feb 16 at 20:06
Relating: unix.stackexchange.com/q/121071/117549
â Jeff Schaller
Feb 16 at 20:06
1
1
Which login shell was assigned to the user?
â steeldriver
Feb 16 at 20:19
Which login shell was assigned to the user?
â steeldriver
Feb 16 at 20:19
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
5
down vote
When you use useradd
you have to specify all sorts of stuff - default shell, home directory, etc. If you aren't seeing a normal bash prompt, I would assume that you didn't specify /bin/bash
as the user's shell and it defaulted to /bin/sh
or similar.
To be honest, useradd
is great for when you are adding users programmatically via a script. Not so great for one-off adding a single user.
Much better to instead use adduser newusername
....
adduser
is good for scripted user creation too - just remember to use--disabled-password
so it doesn't prompt for a password. You can set the password later withecho user:pass | chpasswd
.
â cas
Feb 17 at 0:23
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
When you use useradd
you have to specify all sorts of stuff - default shell, home directory, etc. If you aren't seeing a normal bash prompt, I would assume that you didn't specify /bin/bash
as the user's shell and it defaulted to /bin/sh
or similar.
To be honest, useradd
is great for when you are adding users programmatically via a script. Not so great for one-off adding a single user.
Much better to instead use adduser newusername
....
adduser
is good for scripted user creation too - just remember to use--disabled-password
so it doesn't prompt for a password. You can set the password later withecho user:pass | chpasswd
.
â cas
Feb 17 at 0:23
add a comment |Â
up vote
5
down vote
When you use useradd
you have to specify all sorts of stuff - default shell, home directory, etc. If you aren't seeing a normal bash prompt, I would assume that you didn't specify /bin/bash
as the user's shell and it defaulted to /bin/sh
or similar.
To be honest, useradd
is great for when you are adding users programmatically via a script. Not so great for one-off adding a single user.
Much better to instead use adduser newusername
....
adduser
is good for scripted user creation too - just remember to use--disabled-password
so it doesn't prompt for a password. You can set the password later withecho user:pass | chpasswd
.
â cas
Feb 17 at 0:23
add a comment |Â
up vote
5
down vote
up vote
5
down vote
When you use useradd
you have to specify all sorts of stuff - default shell, home directory, etc. If you aren't seeing a normal bash prompt, I would assume that you didn't specify /bin/bash
as the user's shell and it defaulted to /bin/sh
or similar.
To be honest, useradd
is great for when you are adding users programmatically via a script. Not so great for one-off adding a single user.
Much better to instead use adduser newusername
....
When you use useradd
you have to specify all sorts of stuff - default shell, home directory, etc. If you aren't seeing a normal bash prompt, I would assume that you didn't specify /bin/bash
as the user's shell and it defaulted to /bin/sh
or similar.
To be honest, useradd
is great for when you are adding users programmatically via a script. Not so great for one-off adding a single user.
Much better to instead use adduser newusername
....
answered Feb 16 at 20:56
ivanivan
3,1271213
3,1271213
adduser
is good for scripted user creation too - just remember to use--disabled-password
so it doesn't prompt for a password. You can set the password later withecho user:pass | chpasswd
.
â cas
Feb 17 at 0:23
add a comment |Â
adduser
is good for scripted user creation too - just remember to use--disabled-password
so it doesn't prompt for a password. You can set the password later withecho user:pass | chpasswd
.
â cas
Feb 17 at 0:23
adduser
is good for scripted user creation too - just remember to use --disabled-password
so it doesn't prompt for a password. You can set the password later with echo user:pass | chpasswd
.â cas
Feb 17 at 0:23
adduser
is good for scripted user creation too - just remember to use --disabled-password
so it doesn't prompt for a password. You can set the password later with echo user:pass | chpasswd
.â cas
Feb 17 at 0:23
add a comment |Â
2
Are you certain that you used the hyphen in the
su - user
?â Jeff Schaller
Feb 16 at 20:05
1
Relating: unix.stackexchange.com/q/121071/117549
â Jeff Schaller
Feb 16 at 20:06
1
Which login shell was assigned to the user?
â steeldriver
Feb 16 at 20:19