You are not logged in.
Pages: 1
Hello. I have read that with systemd it's not more necesary to put the user in the diferent groups (sys, disk, lp, network, video, audio, optical, storage, scanner, power, etc.).
But, if I don't add the user to wheel, how do I have to configure sudo? Is there any problem adding the user to wheel?
Last edited by logos88 (2013-04-05 09:11:34)
Offline
Look at: Wiki article about sudo
/etc/sudoers (it is all explained in the file).
man sudoers
In the past, it was recommended to edit the sudoers file only through visudo, because it performs a syntax check, but you should not worry too much, as long as you have a root account.
EDIT: Never mind. I got it the wrong way. You asked about systemd and the wheel group. Sudo only works with groups and users, so if you have to use sudo, then it is safe to do so by adding your user to the wheel account. It does not bother systemd.
Last edited by Awebb (2013-04-02 14:16:15)
Offline
I still edit it with
# visudo
Yeah, same here. It's worth noting that you can change the editor visudo uses (see the man page) - though this is not especially relevant to the original question.
Just a general point, it is worth at least a skim of the sudoers and sudo man pages, and the sudoers comments.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Hello. I have read that with systemd it's not more necesary to put the user in the diferent groups (sys, disk, lp, network, video, audio, optical, storage, scanner, power, etc.).
Oh, I hate that section. It never works for me! I always read it and then I remove myself from all of those groups and then everything stops working correctly.
Offline
Finally I included the user only in the groups wheel and systemd-journal.
In the Users and Groups page (https://wiki.archlinux.org/index.php/Users_and_Groups) says that wheel will be used in the future by systemd to allow starting/stopping services as non-root, and that systemd-journal provides access to the complete systemd logs. Otherwise, only user generated messages are displayed.
Then I made a visudo and uncomented:
#%wheel ALL=(ALL) ALL
Now sudo works good, and I don't have any problems with audio or media devices despite not being in any other groups.
Offline
I'm glad you got it worked out. Please add [Solved] to your thread title.
All the best,
-HG
Offline
Pages: 1