Conversation
|
|
||
| ==== Gain root rights for admin user's | ||
| ---- | ||
| $ sudo adduser --home /home-local/Admin Admin --force-badname |
There was a problem hiding this comment.
why do you use Admin with capital A? we always use lower case names for accounts
There was a problem hiding this comment.
yes with a capital A, admin is already a group.
There was a problem hiding this comment.
how about stud-admin user, then?
| $ sudo adduser Admin sudo | ||
| $ sudo nano /etc/sudoers | ||
| ##add to the list### | ||
| stud-admin ALL=(ALL) NOPASSWD: ALL |
There was a problem hiding this comment.
does this mean we can delete stud-admin?
There was a problem hiding this comment.
yes, stud-admin has still sudo rights, but it is a pool account and not a local one. This user is also the administrator for cob-kitchen-svr
cob-stud-clients/cob-stud-execute.sh
Outdated
| client_list=" | ||
| cob-stud-1 | ||
| cob-stud-2 | ||
| cob.stud-2 |
| @@ -0,0 +1,33 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
is this well tested? can this be used for the robot pcs too?
There was a problem hiding this comment.
tested and adapted for the robots! ipa320/setup_cob4#51
There was a problem hiding this comment.
please consider updated scripts for robot as proposed in ipa320/setup_cob4#84
is it possible to make the pcs list configurable from outside of the script and use the functional part for both robots and cob-stud-pcs.... ➡️ harmonization and less maintenance...
3 participants
No description provided.