Click the button below to set up the scenario.

Two users, bob and jim, currently share the same group id. User jim is being moved to another project, and he needs to be given his own group id.

Modify the user account information so that jim keeps his current user id but moves to a new group called "hoho". You have to create that new group. Make sure his home directory and all files are changed too.

This button checks to see if you have completed the task.

Once you have completed the task, click on this button to remove the scenario.

This button below sets up the scenario.

User "bill" reports that when he tries to log in, the system immediately kicks him out. He tells you that his password is "bill" (i.e. the same as his username). He accidentally left himself logged in during a lab and maybe someone did something to his account?

You should never ask for a user's password to test something about their login. Instead, you can do

  sudo -u bill -i whoami
  

This runs the "whoami" command as user "bill", but the "-i" flag says that sudo should pretend to login as the user first. This means sudo runs all the login scripts and aliases a user gets when they log in. Without "-i" it just runs the command as that user without setting up the environment like "bill" would have.

If "bill" can log in properly and run commands, this sudo command will print the string "bill". If "bill" cannot log in properly then nothing will be printed.

HINT: As this is affecting only bill, check his shell (such as .bashrc or .bash_profile) files first. You can test the fault by trying to login as bill using ssh.

This button checks to see if you have completed the task.

Once you have completed the task, click on this button to remove the scenario.

Press the button below to set up the scenario.

User "ben" reports that after he logs in, he is unable to create any files or directories in his home directory. He tells you that his password is "ben" (i.e. the same as his username). Fix his account appropriately so he can create files and directories again in his home. Use the "sudo su - ben" to become ben and CTRL+D to return to alice as before to check your fix.

This button checks to see if you have completed the task.

Once you have completed the task, click on this button to remove the scenario.

The button below sets up the scenario.

User "amy" reports that after she logs in, the "ls" command appears to do nothing. Her password is "amy". Restore the ls command behaviour to normal.

As always something like "sudo -u amy -i ls /" would demonstrate any issues after amy logs on.

HINT: Aliases can be used to change command behaviours. If you run "alias -p" as amy using sudo (remember the -i) maybe you can see something?

This button checks to see if you have completed the task.

Once you have completed the task, click on this button to remove the scenario.