&gt;&gt;&gt; /etc/sudoers: syntax error near line 23 &lt;&lt;&lt; &gt;&gt;&gt; /etc/sudoers: syntax error near line 26 &lt;&lt;&lt; sudo: parse error in /etc/sudoers near line 23 sudo: no valid sudoers sources found, quitting sudo: unable to initialize policy plugin   no way sudo is not ,have tried quite a few things too
17150
How do I edit an invalid sudoers file? It throws the below error and it's not allowing me to edit again to fix it.  Here is what happens:  $ sudo visudo &gt;&gt;&gt; /etc/sudoers: syntax error near line 28 &lt;&lt;&lt; sudo: parse error in /etc/sudoers near line 28 sudo: no valid sudoers sources found, quitting
58188
I entered chmod -R 777 /usr/bin and now sudo is not working.  It says sudo must be setuid root.  Some advice online said to run chown root:root /usr/bin/sudo chmod 4755 /usr/bin/sudo.  On entering chown root:root /usr/bin/sudo it shows an opened in readonly mode error.
81316
Sample command:  drush cc all   works, but this:  sudo drush cc all   gives me:  sudo: drush: command not found   Why? How to fix this?
50998
Accidentally removed my gnome desktop and am stuck in tty1. Trying to reinstall the desktop and keep getting the error "user is not in the sudoers file". Having trouble adding my user, new to debian and am not sure how to correctly open/edit sudoers from tty1 (or really how to edit files from cmd line for that matter if someone could please lend some specifics)!
23594
To run programs as sudo without password, I edited /etc/sudoers with wrong content.   Then I re-edited it with Mac's default text editor(course sudo cannot be used when /etc/sudoers is wrong).  I tried to run sudo agin, and get this error:   sudo: /etc/sudoers is owned by uid 501, should be 0 sudo: no valid sudoers sources found, quitting   What should I do? I cannot remember the root password (maybe I haven't ever set root password before).
113290
I have PATH=foo set in /etc/profile  According to /etc/password the root and myaccount users have /bin/bash as the login shell.  When I log in as myaccount, the PATH has been set correctly from /etc/profile. If I then sudo su, PATH does not include the value set in /etc/profile.  If I sudo su - instead then /etc/profile is sourced. I know it is good practice to do this anyway but I don't see why it's necessary in order to source /etc/profile.  Why does sudo su clobber PATH, disregarding /etc/profile and how to I make it not?
105633
I am stuck in a login loop because of this error.  I've seen a few threads about this matter but none helped.  I do Ctrl+Alt+f2, when I log in it shows me two errors:  -bash: /home/imight/.profile: line 19 unexpected EOF while looking for matching -bash: /home/imight/.profile: line 22: syntax error: unexpected end of file
18416
I was running a Python script that malfunctioned and used sudo to create a file named &gt;.  How can I get rid of this file?  Of course, when I try sudo rm &gt;, I get the error bash: syntax error near unexpected token 'newline', because it thinks I'm trying to redirect the output of rm.  Its permissions are -rw-r--r--.
38670
i installed a new Debian on a small VPS and now when i try to install sudo i just get this message. I also tried to add FTP-Server into the list and i still get that error.  root@srv45758:~# vi /etc/apt/sources.list deb http://ftp.de.debian.org/debian/ jessie main contrib non-free deb http://ftp.de.debian.org/debian/ main contrib non-free deb http://security.debian.org jessie/updates main contrib non-free   Does any one maybe know the problem?
77744
This error occurs whenever I try to work with sudo. I changed the permissions of /var/ folder to 777 and I think this causes the error. Please help me get back a functional sudo and /var.
65697
I accidentally executed the following command on the etc directory:  sudo chmod -R 700 /etc   I know that I have done something very wrong. My terminal now prints:  I have no name!@ubuntu: /$   How can I revert my etc directory to its earlier state?  I tried changing the permissions but it is failing now. Also, it would be very helpful if someone can explain what actually went wrong when I executed that command on etc. It was only file permissions. Then why does the whole system seems completely blown up? Why is it that no login passwords are working now? I know that there is a file in etc directory that has to do with users. But how did changing permissions jeopardize everything? Some technical details about this would be very helpful.
4844
I accidentally executed      sudo chmod -R 777 /   I was actually trying to change a specific folder permission recursively, btw i did stop the command before it changed everything.  But now, i can't execute for example      sudo   Every time i try to sudo something it throws me this error:     effective uid is not 0, is sudo installed setuid root?   Btw i know i can use chown -R root:root /usr/bin where sudo is located, but of course i don't have the permissions to do this.  So, how can i revert this process? Or at least save the sudo file without reinstalling everything?  The system is still connected to the internet and seems to work fine besides the sudo issue.  Thanks in advance.
64283
I have added alias ll='ls -la' in /etc/bash.bashrc but sudo ll is not working. Is there a way to "source" bash.bashrc? In a related post, another user suggesting creating an alias for sudo with a space after it. Eg. alias sudo='sudo ' but there wasn't any context to this answer. Should I add this to my bashrc? Seems hackish.  What is the correct method for adding an alias for my sudo one-off commands?
25948
I'm a first time Linux user. My laptop wasn't connecting to the wifi so I followed the instructions from .  On typing sudo apt-get update after that, I got this error:  E: Type 'sudo' is not known on line 2 in source list /etc/apt/sources.list E: The list of sources could not be read.   What can I do?
83812
I stupidly ran sudo rm /* followed by sudo rm -R /*  My sites still run, although the vast majority of commands like ls are now broken.  Is there a simple way to get data off the server or reverse some of damage?
56449
$ source /etc/environment   $ sudo source /etc/environment  [sudo] password for t:  sudo: source: command not found   It seems that a different shell than bash is run to execute source /etc/environment and that shell doesn't have source as builtin.   But my and the root's default shells are both bash.  $ echo $SHELL /bin/bash   If sudo indeeds uses a different shell, why is it? I saw , but don't understand in my case.
17509
dam@ubuntu:~$ sudo apt-get update   W: Failed ....  adam@ubuntu:~$ sudo apt-get install fetch   Reading package lists... Done   Building dependency tree          Reading state information... Done   E: Unable to locate package fetch