09-16-2003
yes - see the man page for vi
-r filename
Edit filename after an editor or system crash. (Recov-
ers the version of filename that was in the buffer
when the crash occurred.)
If the system crashes, it will have saved your editor session in a recoverable file which is recovered with the -r option. Note that the last few commands, key strokes, may not be there but the majority of any changes will be.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello everybody,
My question is: how to add /tmp/work at the end of line in vi editor.
my file looks like:
cp file1
cp file2
cp file3
****
I need to add " /tmp/work" at the end of each line.
I tried this
:%s/$/" /tmp/work"
and this
:%s/$/\ /tmp/work\/
but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies
2. HP-UX
I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one?
thx (6 Replies)
Discussion started by: diamond
6 Replies
3. UNIX for Advanced & Expert Users
Hi,
how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before.
for exemple if in my file i have
line 1
line 2
I want to have :
start line 1 end
start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies
4. HP-UX
I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work.
how can I enable them.
thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
6. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
7. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
8. Shell Programming and Scripting
How can ` character be printed on vi editor ?
empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies
9. Shell Programming and Scripting
Hello All,
Need one Help for one issue.
I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it.
It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies
10. Open Source
I was looking through the topics and I wasn't sure if this was the best place to post this question:
I was wondering, out of curiosity, which software everyone was using to code their scripts in. I do mostly sh/ksh and my favorite has always been EditPlus because it is small, fast, yet powerful.... (409 Replies)
Discussion started by: yongho
409 Replies
crashdc(8) System Manager's Manual crashdc(8)
NAME
crashdc - Diagnostic data collection for a running or crashed system
SYNOPSIS
/usr/bin/crashdc [system-kernel] [core-image]
DESCRIPTION
The crashdc utility examines the core image of the operating system to extract critical diagnostic data. This utility is a shell script
that invokes several tools and commands that extract selected parameters of a running or a crashed system (for example, system configura-
tion, running processes, and panic messages).
The arguments to the crashdc utility are the system kernel and the core image. The default values are /vmunix and /dev/mem, respectively.
If you specify no arguments, the crashdc utility examines the running system.
The system usually invokes the crashdc utility during system startup. If the most recent core dump has been saved by the savecore command,
both the core image and the system kernel (respectively vmcore.n and vmunix.n, where the variable n is the crash number) are saved in the
crash directory (by default, /var/adm/crash). Also, the crashdc utility saves the output as the file crash-data.n (where the variable n is
the crash number) in the crash directory. The crashdc utility is invoked only if crash-data.n output in the crash directory does not exist
or is not from the most recent crash.
FILES
Default core image Default system image Output from crashdc
SEE ALSO
Commands: dbx(1), kdbx(8), savecore(8)
crashdc(8)