You can use the combination of sudo command (assuming that sudo is configured for your account) to save a file without creating a third file in /tmp. This is useful to write a privileged file with sudo command. For example saving a read-only file edited in vim and vi is possible with this trick.
Syntax to save a file in Vim without root permission with sudo
In this example, you will edit a file called /etc/apache2/conf.d/mediawiki.conf as a normal user:
$ vi /etc/apache2/conf.d/mediawiki.conf
Make some changes and try to save by pressing :w, enter:
To save a file, simply type the following command:
:w !sudo tee %
What the vim and shell command does:
- :w – Write a file (actually buffer).
- !sudo – Call shell with sudo command.
- tee – The output of write (vim :w) command redirected using tee.
- % – The % is nothing but current file name. In this example, it is /etc/apache2/conf.d/mediawiki.conf. In other words tee command is run as root and it takes standard input (or the buffer) and write it to a file represented by %. However, this will prompt to reload file again (hit L to load changes in vim itself):
Update ~/.vimrc file
Open/Edit ~/.vimrc file and append the following code:
" " Sample command W " command W :execute ':silent w !sudo tee % > /dev/null' | :edit! |
Save and close the file. Open vim/vi and try to edit a privileged file with:
$ vi /etc/hosts
Now, write a privileged file with custom command just type W:
Now, sudo requires that you authenticate yourselves with a password:
A note about sudo config
Make sure you add yourself to sudo file. Here is my configuration (run ‘sudo visudo‘ OR ‘su -‘ and ‘visudo‘):
# User privilege specification root ALL=(ALL) ALL %admin ALL=(ALL) ALL |
Make sure you add yourself to admin group:
# usermod -a -G admin vivek
# id vivek
Sample outputs:
uid=501(veryv) gid=20(staff) groups=20(staff),80(admin),81(_appserveradm),98(_lpadmin),33(_appstore),100(_lpoperator),204(_developer)Try vim plugins to write/edit a privileged file or read only file
- User Unix commands including sudo, chmod, and more without leaving vim ever!
- This plugin enables vim to read files, using sudo or su or any other tool that can be used for changing the authentication of a user.
Conclusion
You just learned how to save a read-only file edited in vim text editor. As a sysadmin you might edit a file non-privileged user. In such case you can save file without login as root using the sudo command.
:w !sudo %
does not work for me.
you need to use
:w !sudo tee %
“To save a file, simply type the following command:
:w !sudo %”
you forget tee in command
Wow, I can’t believe I never thought of that before.
I added this to my .vimrc that I sync on every machine I administrate based on what you wrote:
if has(“unix”)
command -nargs=? Swrite :w !sudo tee %
endif
I have a :SudoW command in my vimrc that does exactly this. I got it from some one else’s blog at some point and can’t seem to find out where, at this point. Here is the snippet though.
command! -bar -nargs=0 SudoW :silent exe “write !sudo tee % >/dev/null” | silent edit!
@Sebastian
Thanks for the head up! tee included in screen shot but somehow I forgot in command line.
@James.
Use :w !sudo tee %. It was a typo on my part.
HTH
not working for me
:w !sudo tee%
!sudo teea
[No Valid Runas is Matched]
Sorry, user xxxxx is not allowed to execute ‘teea’ as anyone on newss1.
sudo: teea:command could not found.
Check the path or specify path plus command.
[Hit return to continue]
:q
No write since last change (:quit! overrides)
[Hit return to continue]
Tried with space as well after tee command
Regards,
Manoj
Nice tip, thanks Vivek.
Loved the Tip !!!!
@Manoj,
Put a white space between tee and %
:w !sudo tee %You must configure sudo. You use sudo for admin task, don’t you?, A typical /etc/sudoers for admin users:
And add your self to admin group (use usermod).
This is very useful, thank you for posting it.
@Manoj
seems you are missing a space between tee and % in your command line
both the way i tried, seems sudo is not configured.
I dont have sudo/root permissions, what should i do?
Vivek,
Love it. Thanks for sharing it.
BTW, I tried to reach earlier and your site was down for like hour or two.
@Manoj,
Only root user suppose to access and edit files in /etc. This is not a hacking or creaking attempt.
@Vinod,
Our apologies for the temporary inconvenience. There was some sort of network issue. Let me know if you’ve any more problems.
This is an awesome trick, but I don’t get why the password is not asked ?
This mean whoever get my user access can changes files on /etc/ without knowledge of the sudo password ?
@Nic0,
You must have used sudo earlier. It remembers the password for some time (see sudo man page for more info). Another possibility is – you may have configured sudo without the password.
@Vivek Gite, My mistake, I did probably used sudo before. (and entry the password)
I tried again, and it ask for the password this time. Sorry.
Thanks for the tips anyway.
that one bugged me long enough. Cheers!
This is very useful! Thanks!
Nice – but – sudo on my PC is configured to ask my password for every sudo call.
But then this tip fails, because I can see sudo requesting my password, waiting one second, then, as if I entered a wrong passwd, it fails, until three times, and I get rejected without beeing able to type my password in.
So, will this tip only work if sudo is configured not to ask password?
Did you test it?
If so, do you know why sudo is getting an entry? I do not type anything, but it seems to get some input through the [:w !sudo tee %] command.
Of course, I tried to type in my password – it failed.
@Philippe,
Sudo is also configured here and I’ve no problem. What about passwd_timeout and timestamp_timeout?
@Vivek,
No, that is not related to sudo parameters.
If found this: This tip works for [vi] or [vim],
but I have got this problem only with [gvim] – which is odd but true.
@Philippe,
I see we are talking about GUI here. Have you tried out gui version of sudo gksudo instead of sudo? Try it on dummy file as gksudo some time provides real weird results when combined with shell utilizes (may be steams are not connected but dunno).
HTH
@Vivek,
I just tried gksudo in place of sudo, it fails because :
– I enter :w ! gksudo tee %
– Then, I get a new line – no prompt – I try to enter my password, nothing happens,
I quit by , and then file is overwritten, but emptied by the procedure!
(also tried with gksudo -P)
So, in a way – it works ;-) file is wiped… :-/
That was a nice idea anyway!
grrr WordPress has eaten my words : I typed
I quit by , and then file is overwritten,
Shooot !!! I ***** dislike WordPress text entry !
@Philippe,
I’m out of ideas for gvim here and I guess it is related to GUI. Both stderr and stdout are terminal streams. And GUI version of gvim accept messages from user input devices (??), not from stdin so I guess you are getting empty file as a result. May be you need to patch gksudo to accept stderr or come with some sort of wrapper (we do this all the time with php-cgi and perl cgi fastcgi). Please update us if you find any other solution to your problem.
Nice tip..but unfortunately it doesn’t work for me. I have followed discussion here and implemented the same thing …oh forget to tell that I am on Gentoo.
1)I have used sudo before run this command..(so that’s in history)
2)say I have open /etc/ntp.conf and once I passed the recommendation like this
:w !sudo tee %
it asked for password(that’s fine..if the time elapsed)
but says “Press enter to continue..”
@ Vivek
any idea??
Cheers!
No idea, check /var/log/secure (RHEL / CentOS) or /var/log/auth.log (Debian and friends) logs details about sudo command and failed attempts. This may provide additional help. I’ve used this many times under Debian and RHEL based servers.
This is neat. However, why not run Vi as root in the beginning? i.e.,
$ sudo vi /etc/fstabHow stupid can this post possibly get? If a username is already in sudo then he/she can just become root and edit a file.
If a username is configured only to do certain things like edit config files then there should be be no problem in editing that file to begin with, just use “sudo su”.
Exactly, this is a good post because if you are vim’ing a file and have spent a lot of time and effort, and then realize you don’t have rights to :w the edits, then this is a perfect quick solution.
@Shane shouldn’t be calling anyone stupid when your typing sudo su. Try reading the sudo man page. The purpose of the post was to show you how to edit a file, you don’t have permissions to, without closing your editor and opening it again within sudo.
There is also this Plugin SudoEdit.vim available, which provides the commands :SudoWrite and :SudoRead and uses TabCompletion for filenames. You can configure it to use sudo or su or even ssh.
http://www.vim.org/scripts/script.php?script_id=2709
Nice find :)
this will work only the user is sudo user.
@ all,
i need to configure insult para in sudo file after given correct para it doesn’t work for me any ideas…?
para :- Defaults instults
:wq!
but same message shown after configure “Sorry, try again.”
:w !sudo tee %
says:
:w !sudo tee %
Password:Sorry, try again.
Password:
Sorry, try again.
Password:
Sorry, try again.
sudo: 3 incorrect password attempts
shell returned 1
Press ENTER or type command to continue
how do we disable this option in linux since there are chances for the users to edit the files
Please help me! ANYONE !?!?!
As you can see I’m a noob… please help me :D
I logged in a ‘root’ etc but when I used this command ‘vi BLAHBLAH.conf’
I can’t edit anything ;( why is this and how do I fix?
Wow! Kudos on your excellent hack!
I think a nicer solution that doesn’t require piping the document through tee would be to write it to a temporary file and then sudo mv tmp % – more complex to type in but if you are mapping it as a command it can be as complex as needed.
If you are using this method, constantly forgetting what user account you are using, you might not want to be editing a root owned file. Maybe. If you MUST create sudo rules, specify them. Telling a new Linux user/admin to use the admin group, and then allow ALL COMMANDS to ALL HOSTS? I simply have nothing nice to say about it. Instead, I would refer you to a book called “Sudo Mastery” by Michael W. Lucas, and wish you the best of luck.