08-23-2001
It is after the fact, but in the future you can attempt a recover by forcing the editor to preserve your buffer. You will find this useful if you have made edits, then discover that you can't save your edits. You can then use the vi -r <file> to recover the buffer after you close.
If the file system is full you can also delete something with :! rm <junkfile> the !(bang) allows you to issue unix commands within the editor, like : !df to see the space.
Best case, write the file to a directory in another filesystem that has space available with :w /usr/local/../.../file
Daivd
10 More Discussions You Might Find Interesting
1. Solaris
Recovering Solaris to an alternate server
I was just wondering if anyone could give me some points on restoring a Solaris 9 backup to an alternate server. Basically, we use netbackup 6 and I was wondering what the best procedures are for doing this? What things do we need to take into... (3 Replies)
Discussion started by: aaron2k
3 Replies
2. UNIX for Dummies Questions & Answers
Hi, I am new to unix and I set a password for a user and now I need to recover what that password was. Is there a way, where as root, I can view what a users passwords is?
Thanks,
Eric (2 Replies)
Discussion started by: ejbrever
2 Replies
3. Forum Support Area for Unregistered Users & Account Problems
hello,
my password got lost - and your service to generate new passwords does not work -ive tried it out 50 times the last week or so, never got a single mail from it...
please generate a new password for my account "congo" with mailadress.
thanks.
Thomas (3 Replies)
Discussion started by: congo00000001
3 Replies
4. Solaris
Hi all,
how i recovery the files when system is crash? (using crashdump concept)
regards
Krishna (1 Reply)
Discussion started by: murthy76
1 Replies
5. Cybersecurity
I am trying to access an old email account but cannot recall the password and the backup email account has been closed, also. I need instructions or an expert who can assist recovering my password for web-based email account. (4 Replies)
Discussion started by: pp_mcgee
4 Replies
6. Red Hat
Is there a way to recover the ldap server if it crashes (4 Replies)
Discussion started by: nalcomis
4 Replies
7. UNIX for Advanced & Expert Users
Hi,
Please let me know the way to recover the files deleted from home directory by 'rm*' command .
Thanks in advance. (10 Replies)
Discussion started by: ravigupta2u
10 Replies
8. Red Hat
The situation: i try to boot centos in new environement(the vg name is changed) i edit the menu.lst of grub,did grub-install,then mkinitrd `uname -r`.img `uname -r` but when i reboot the new vg is not find and i obtain only a kernel panic :( (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
9. UNIX for Dummies Questions & Answers
I had a data folder in MySQL that has simply disappeared. Something about a compromised server and MySQL crashing. This happened a few days ago. Although there has been one reboot, nothing new has been written to the server, so I'm thinking in theory it might still be there.
Has anyone had... (2 Replies)
Discussion started by: SurfMe69
2 Replies
10. Solaris
Hi,
I need to recover the Solaris 11 OS, and it backup via Netbackup 7.6 file level backup only. Does anyone know what are steps to recover it? Thanks. :confused::confused::confused: (3 Replies)
Discussion started by: freshmeat
3 Replies
EX(1) General Commands Manual EX(1)
NAME
ex, edit - text editor
SYNOPSIS
ex [ - ] [ -v ] [ -t tag ] [ -r ] [ +command ] [ -l ] name ...
edit [ ex options ]
DESCRIPTION
Ex is the root of a family of editors: edit, ex and vi. Ex is a superset of ed, with the most notable extension being a display editing
facility. Display based editing is the focus of vi.
If you have not used ed, or are a casual user, you will find that the editor edit is convenient for you. It avoids some of the complexi-
ties of ex used mostly by systems programmers and persons very familiar with ed.
If you have a CRT terminal, you may wish to use a display based editor; in this case see vi(1), which is a command which focuses on the
display editing portion of ex.
DOCUMENTATION
The document Edit: A tutorial (USD:14) provides a comprehensive introduction to edit assuming no previous knowledge of computers or the
UNIX system.
The Ex Reference Manual - Version 3.7 (USD:16) is a comprehensive and complete manual for the command mode features of ex, but you cannot
learn to use the editor by reading it. For an introduction to more advanced forms of editing using the command mode of ex see the editing
documents written by Brian Kernighan for the editor ed; the material in the introductory and advanced documents works also with ex.
An Introduction to Display Editing with Vi (USD:15) introduces the display editor vi and provides reference material on vi. In addition,
the Vi Quick Reference card summarizes the commands of vi in a useful, functional way, and is useful with the Introduction.
FILES
/usr/share/misc/exstrings error messages
/usr/libexec/exrecover recover command
/usr/sbin/expreserve preserve command
/etc/termcap describes capabilities of terminals
~/.exrc editor startup file
/tmp/Exnnnnn editor temporary
/tmp/Rxnnnnn named buffer temporary
/usr/preserve preservation directory
SEE ALSO
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7)
AUTHOR
Originally written by William Joy
Mark Horton has maintained the editor since version 2.7, adding macros, support for many unusual terminals, and other features such as word
abbreviation mode.
BUGS
The undo command causes all marks to be lost on lines changed and then restored if the marked lines were changed.
Undo never clears the buffer modified condition.
The z command prints a number of logical rather than physical lines. More than a screen full of output may result if long lines are
present.
File input/output errors don't print a name if the command line `-' option is used.
There is no easy way to do a single scan ignoring case.
The editor does not warn if text is placed in named buffers and not used before exiting the editor.
Null characters are discarded in input files, and cannot appear in resultant files.
4th Berkeley Distribution October 21, 1996 EX(1)