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
LEARN ABOUT DEBIAN
vileget
VILEGET(1) User Contributed Perl Documentation VILEGET(1)
NAME
vileget - Pass file edit requests to a Vile editor running Vileserv.
SYNOPSIS
vileget [-n] [-d] [-w] [-s socket-path] [-c command] [-C command] [file ...]
DESCRIPTION
Vileget can be used to load files into an already running instance of Vile or XVile. The editor should have already loaded and started the
Vileserv perl module. (See the Vileserv documentation for more detail.)
By default, if vileget cannot connect to a running instance of the editor it tries to start a new one. This will only work correctly if
you have configured Vile to start Vileserv automatically. (Vileget will try to find an XVile binary first, then look for a Vile binary.)
Vileget looks for the Vileserv socket in the user's home directory ($HOME/.vilesock) by default. This can be changed by setting the
VILESOCK environment variable, or by using the -s option.
If vileget is handed a directory name, it trys to get the target Vile to load the directory.pm module and popup the appropriate directory
listing. This only works for the first directory mentioned on the command line, and it only works if the target Vile is configured to
accept remote commands (see the -c/-C options).
COMMAND-LINE OPTIONS
-d With this option, vileget will change the current working directory of the running Vile to be the directory in which vileget is being
run, in addition to loading any requested files.
-n This tells vileget NOT to try starting a new instance of Vile if necessary. If vileget cannot connect to a running Vile, it will just
die with a connection error instead.
-w Vileget waits for given file(s) to be written by Vile before exiting.
-s socket-path
Tells vileget to use the socket given by socket-path. This overrides the default and the environment variable VILESOCK.
-c command
-C command
The -c and -C options can be used to pass arbitrary Vile commands to a running instance of Vile. These can be used at the same time
that file edits are being requested, or without giving any files at all. When file arguments are used, the -c option can be used to
execute a Vile command before the requested files are loaded. The -C option is used to execute a Vile command after the requested
files are loaded. If no file arguments are given, then -c and -C are basically the same, except that -c has precedence. These
options are non-repeatable, so you can only execute two Vile commands per invocation of vileget. Of course, there are always
procedures...
You can have a lot of mindless fun with these two options. For example, you can popup and close the buffer list by repeatedly
executing:
vileget -c '*'
As a nod towards security, command execution is disabled by default in Vileserv. To enable it, you can use
setv %vileserv-accept-commands true
in your .vilerc file. Note that running something like
vileget -c 'setv %vileserv-accept-commands false'
can be used to disable remote commands dynamically. Naturally, this is considered to be both a security violation *and* a feature...
Passing arbitrary commands to Vile may well produce arbitrary results. The author assumes no liability for edit sessions that have
collapsed into singularities, or, as a matter of fact, for anything else.
SEE ALSO
vileserv(3), vile(1)
AUTHOR
J. Chris Coppick, 1998 (last updated: July 26, 2000)
perl v5.14.2 2012-06-03 VILEGET(1)