I just ran into a problem in which I got myself cornered. I’ve edited a configuration file with elevated permission using sudo:
sudo vim /etc/httpd/conf.d/metrics.conf
From time to time when editing, I background the vim session in order to perform some commands in the shell, then continue working in vim. This time, I’ve sent the editor into the background. When trying to foreground it I got this:
~/Metrics(branch:bug_947304*) » fg [1] + 11403 continued sudo vim /etc/httpd/conf.d/metrics.conf [1] + 11403 suspended (tty input) sudo vim /etc/httpd/conf.d/metrics.conf
What? How? When? Any attempt to foreground this process failed. Reason was the elevated permission I’ve started the editor with. Long story short, you’ll need to kill the editor in order to get back into editing. This mailing list thread explains why.
Romanofskis Blog 