I'm running full DRBL mode (Fedora Core 7) and I have a burn in program that need access to the hard drive and memory. I get errors stating that I need to be root to test these devices. I've created a sudo group and added all of the drbl* users to it and can sudo no problem on the local server. When I boot up my thin client the users are not shown in the user/groups widget and can not sudo.
Thanks
JS
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So you mean you do not have root password ? Like Ubuntu does ?
Actually 2 options for you:
1. Set root password of clients in server by:
/opt/drbl/sbin/drbl-client-root-passwd
Then you can login client's console as root, run "visudo" to edit the sudo users.
2. Edit /tftpboot/nodes/$IP/et/sudoers manually. (You have to pay attention to its rw permission)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running full DRBL mode (Fedora Core 7) and I have a burn in program that need access to the hard drive and memory. I get errors stating that I need to be root to test these devices. I've created a sudo group and added all of the drbl* users to it and can sudo no problem on the local server. When I boot up my thin client the users are not shown in the user/groups widget and can not sudo.
Thanks
JS
You have to edit /etc/sudores in the clients. An easier way is you edit one, then use
/opt/drbl/sbin/drbl-cp-host
to copy it to all of the clients.
How do I edit the sudoers file on the client without being able to use sudo?
So you mean you do not have root password ? Like Ubuntu does ?
Actually 2 options for you:
1. Set root password of clients in server by:
/opt/drbl/sbin/drbl-client-root-passwd
Then you can login client's console as root, run "visudo" to edit the sudo users.
2. Edit /tftpboot/nodes/$IP/et/sudoers manually. (You have to pay attention to its rw permission)