# Visudo\_wheelgroup or drop-in file

**URL:** <https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513>\
**Category:** Newbie\
**Created:** [April 28, 2024, 11:02am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513 "2024-04-28T11:02:52Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:02am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/1 "2024-04-28T11:02:52Z")

</div>

Hi,

not very happy about this, lol just having a bad day. Just spent nearly 2hrs just trying to be able to allow my user to be able to use sudo without a password. Still haven’t been able to do it.

I’ve edited visudo

exported $EDITOR=vim

my user is in groups sys rfkill wheel slim

I un-commented the wheel group without password

rebooted few times

Any help would be much appreciated.

Cheers.

```auto
103 ## User privilege specification
104 ##
105 root ALL=(ALL:ALL) ALL
106 
107 ## Uncomment to allow members of group wheel to execute any command
108 # %wheel ALL=(ALL:ALL) ALL
109 
110 ## Same thing without a password
111 %wheel ALL=(ALL:ALL) NOPASSWD: ALL
112 

[slim@AnNasrun ~]$ groups slim
sys wheel rfkill slim

```

Apologies if this is just some basic mistake. I’ve tried and can’t work it out.

---

<div class="post-metadata">

**Author:** ![r0ckhopper](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/r0ckhopper/32/51768_2.png) [@r0ckhopper](https://forum.endeavouros.com/u/r0ckhopper)\
**Post date:** [April 28, 2024, 11:07am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/2 "2024-04-28T11:07:21Z")

</div>

> [@muj](#):
>
> Just spent nearly 2hrs just trying to be able to allow my user to be able to use sudo without a password

Why!?!!

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:09am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/3 "2024-04-28T11:09:33Z")

</div>

lol Why what?

Why allow my user to do that? Because it should be an easy change and I’m lazy and wanted to do it for a period of time and then change it back.

---

<div class="post-metadata">

**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\
**Post date:** [April 28, 2024, 11:23am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/4 "2024-04-28T11:23:39Z")

</div>

```auto
<Your-User> ALL=(ALL:ALL) NOPASSWD: ALL

```

As the last line when you `sudo visudo`

e.g.

```auto
xircon ALL=(ALL:ALL) NOPASSWD: ALL

```

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:26am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/5 "2024-04-28T11:26:00Z")

</div>

I’m sorry I should have said I did try that first.

---

<div class="post-metadata">

**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\
**Post date:** [April 28, 2024, 11:26am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/6 "2024-04-28T11:26:33Z")

</div>

It works, you may need to log off/on.

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:27am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/7 "2024-04-28T11:27:20Z")

</div>

Okay, I’ll try it again and copy/paste what Ive done be back after rebooting.

Thanks xircon

---

<div class="post-metadata">

**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\
**Post date:** [April 28, 2024, 11:30am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/8 "2024-04-28T11:30:02Z")

</div>

```auto
## sudoers file.
##
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
##
## See the sudoers man page for the details on how to write a sudoers file.
##

##
## Host alias specification
##
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias	WEBSERVERS = www1, www2, www3

##
## User alias specification
##
## Groups of users. These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias	ADMINS = millert, dowdy, mikef

##
## Cmnd alias specification
##
## Groups of commands. Often used to group related commands together.
# Cmnd_Alias	PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# /usr/bin/pkill, /usr/bin/top
#
# Cmnd_Alias	REBOOT = /sbin/halt, /sbin/reboot, /sbin/poweroff
#
# Cmnd_Alias	DEBUGGERS = /usr/bin/gdb, /usr/bin/lldb, /usr/bin/strace, \
# /usr/bin/truss, /usr/bin/bpftrace, \
# /usr/bin/dtrace, /usr/bin/dtruss
#
# Cmnd_Alias	PKGMAN = /usr/bin/apt, /usr/bin/dpkg, /usr/bin/rpm, \
# /usr/bin/yum, /usr/bin/dnf, /usr/bin/zypper, \
# /usr/bin/pacman

##
## Defaults specification
##
## You may wish to keep some of the following environment variables
## when running commands via sudo.
##
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
##
## Run X applications through sudo; HOME is used to find the
## .Xauthority file. Note that other programs use HOME to find   
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
##
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
##
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
##
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
##
## Uncomment to enable special input methods. Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
##
## Uncomment to use a hard-coded PATH instead of the user's to find commands
# Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
##
## Uncomment to restore the historic behavior where a command is run in
## the user's own terminal.
# Defaults !use_pty
##
## Uncomment to send mail if the user does not enter the correct password.
# Defaults mail_badpass
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot. Use sudoreplay to play back logged sessions.
## Sudo will create up to 2,176,782,336 I/O logs before recycling them.
## Set maxseq to a smaller number if you don't have unlimited disk space.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!REBOOT !log_output
# Defaults maxseq = 1000
##
## Uncomment to disable intercept and log_subcmds for debuggers and
## tracers. Otherwise, anything that uses ptrace(2) will be unable
## to run under sudo if intercept_type is set to "trace".
# Defaults!DEBUGGERS !intercept, !log_subcmds
##
## Uncomment to disable intercept and log_subcmds for package managers.
## Some package scripts run a huge number of commands, which is made
## slower by these options and also can clutter up the logs.
# Defaults!PKGMAN !intercept, !log_subcmds

##
## Runas alias specification
##

##
## User privilege specification
##
root ALL=(ALL:ALL) ALL

## Uncomment to allow members of group wheel to execute any command
# %wheel ALL=(ALL:ALL) ALL

## Same thing without a password
# %wheel ALL=(ALL:ALL) NOPASSWD: ALL

## Uncomment to allow members of group sudo to execute any command
# %sudo	ALL=(ALL:ALL) ALL

## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw # Ask for the password of the target user
# ALL ALL=(ALL:ALL) ALL # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d
@includedir /etc/sudoers.d

xircon ALL=(ALL:ALL) NOPASSWD: ALL

```

This is the full file (working here, haven’t entered a sudo password since 1999 😃 ).

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:36am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/9 "2024-04-28T11:36:19Z")

</div>

> [@xircon](#):
>
> This is the full file (working here, haven’t entered a sudo password since 1999 😃 ).

hahaha nice.

it’s still asking me

```auto
[slim@AnNasrun ~]$ sudo ls
[sudo] password for slim:

97 
 98 ##
 99 ## Runas alias specification
100 ##
101 
102 ##
103 ## User privilege specification
104 ##
105 root ALL=(ALL:ALL) ALL
106 
107 ## Uncomment to allow members of group wheel to execute any command
108 # %wheel ALL=(ALL:ALL) ALL
109 
110 ## Same thing without a password
111 %wheel ALL=(ALL:ALL) NOPASSWD: ALL
112 slim ALL=(ALL:ALL) NOPASSWD: ALL
113 
114 ## Uncomment to allow members of group sudo to execute any command
115 # %sudo ALL=(ALL:ALL) ALL
116 
117 ## Uncomment to allow any user to run sudo if they know the password
118 ## of the user they are running the command as (root by default).

```

maybe i need to put my user at the bottom like yours?

but it should work the way i’ve done it right?

---

<div class="post-metadata">

**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\
**Post date:** [April 28, 2024, 11:43am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/10 "2024-04-28T11:43:33Z")

</div>

No - has to be last line of file, as I said above.

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:44am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/11 "2024-04-28T11:44:50Z")

</div>

lol I swear I’m sure I’ve done it like that before.

hold up tho I’m just writing something to add here

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:45am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/12 "2024-04-28T11:45:51Z")

</div>

lol This will sound stupid to lol everyone I think but…

I’m going to reinstall vanilla Arch. It’s best Imo that I have less features and only get features when I’ve learnt about them and configured them so I understand them.

I haven’t come across a better Linux community than here at EnOS so I really hope that I’ll still be welcome here even though I’ll be running vanilla Arch.

---

<div class="post-metadata">

**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\
**Post date:** [April 28, 2024, 11:47am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/13 "2024-04-28T11:47:02Z")

</div>

Endeavour is pretty much vanilla arch, it just has an installer and some themes, that is it.

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 11:54am UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/14 "2024-04-28T11:54:20Z")

</div>

lol, yeah lol but not to someone like me.

you should see an earlier post of mine about how I was stuck and thought the computer was broke lol coz I was accidentally enabling this feature called blur lock. Took me ridiculous amounts of time to work out I just needed to not do it lol or comment it out. lol damn man.

On my Arch install honestly I had no issues really. Of course it didn’t look as nice, but I could search for files was it with rofi, i had a terminal file manager, had vim setup with plugins with vim.plug manager. had alacritty themed and customised as i wanted had setup picom and dunst made all dark theme and much more stuff can’t remember.

yeah just going to do that and then at least I know what it should be and hopefully can troubleshoot better.

lol when I first came on here my gosh I spent hours thinking why cant I run `sudo mkinitcpio -P` I installed mkinitcpio reinstalled kernels different kernels, reinstalled lol the whole os about 3-4 times again did more can’t even think about it.

Let me say to anyone reading this… THIS IS JUST MY STUPIDITY. Nothing to do with EnOS.

---

<div class="post-metadata">

**Author:** ![UncleSpellbinder](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/unclespellbinder/32/127055_2.png) [@UncleSpellbinder](https://forum.endeavouros.com/u/UncleSpellbinder)\
**Post date:** [April 28, 2024, 2:37pm UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/15 "2024-04-28T14:37:48Z")

</div>

> [@xircon](#):
>
> Endeavour is pretty much vanilla arch, **it just has an installer and some themes, that is it**.

I have to disagree. The are plenty more Endeavour-specific things included besides _just the installer and some themes._ The Welcome app alone shows plenty of Endeavour-specific helpers not included in a vanilla Arch install. Plus EOS has `rebuild-detector` installed by default (vanilla Arch does not), which was valuable with the recent Python update.

Just one of the many examples would be the EndeavourOS Quickstart Installer.

 ![Screenshot from 2024-04-28 09-34-48](https://forum.endeavouros.com/uploads/default/original/3X/9/a/9afea54034c03dcd2f207e79381ae621a7dee4fa.png)

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 2:44pm UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/16 "2024-04-28T14:44:55Z")

</div>

lol yep for sure and that is because the devs have put in a lot of effort.

Moved from mkinitcpio to dracut  
on i3: dunst, pimoc, probably lxappearance, environment variables, loads of things all over the place. lol and much more probably that I don’t have a clue about.

---

<div class="post-metadata">

**Author:** ![UncleSpellbinder](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/unclespellbinder/32/127055_2.png) [@UncleSpellbinder](https://forum.endeavouros.com/u/UncleSpellbinder)\
**Post date:** [April 28, 2024, 2:50pm UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/17 "2024-04-28T14:50:11Z")

</div>

> [@muj](#):
>
> and that is because the devs have put in a lot of effort.

100% accurate. The EOS dev team may be small compared to other distros, but the work they do to provide a fantastic OS for the end-user is phenomenal. They all have day jobs and a life outside the world of Linux. They do fantastic work to keep EndeavourOS the amazing distro that it is.

---

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [April 28, 2024, 2:56pm UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/18 "2024-04-28T14:56:16Z")

</div>

It sounds like you have already moved on but the reason is that sudo uses drop-ins now.

The drop ins override sudoers.conf.

That way you never have to edit sudoers.conf directly.

We include a drop-in that you needed to edit or remove.

---

<div class="post-metadata">

**Author:** ![muj](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/muj/32/94382_2.png) [@muj](https://forum.endeavouros.com/u/muj)\
**Post date:** [April 28, 2024, 2:57pm UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/19 "2024-04-28T14:57:09Z")

</div>

Big Hello @dalto

yeah that’s what I mean. Too many things changed for me.

I’m more than happy to spend lol days troubleshooting (coz I’m not too bright) but I don’t like to do it when I’ve already done it.

Yeah, I’m back on Arch. wasn’t difficult as had backed up my configs and package list.

Just hope I can stay on this forum though.

---

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [April 28, 2024, 3:38pm UTC](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513/20 "2024-04-28T15:38:01Z")

</div>

> [@muj](#):
>
> yeah that’s what I mean. Too many things changed for me.

I guess my point is that it changed everywhere, not just on EOS. `sudo` itself added that functionality. Even for your manual changes it is better to use drop-ins at this point.

> [@muj](#):
>
> Just hope I can stay on this forum though.

You are welcome to continue to be part of this forum even if you are currently using a different distro.

However, if you have technical questions, please mention that you are using Arch so we can provide better answers.

[Next page](https://forum.endeavouros.com/t/visudo-wheelgroup-or-drop-in-file/54513.md?page=2)
