06-15-2001
split the file
from the vi man pages....
When editing a very large file (greater than approximately 9,070,000
characters), you may get the following warning message: Warning: Tmp
file too large. See vi(1). This does not mean your system has run
out of space in /tmp. It is warning you that vi (i.e. the ex family
of editors) cannot track your changes in the temporary files the
editor maintains during an edit session. The following cautions are
advised: If the editor crashes (i.e. system halts, or accidental
process termination), a preserve file cannot be created and you will
not be able to recover your changes via the recover feature. In
addition, if while editing a very large files and vi fails to come up
in visual mode, do not write this file (:w) since it may be
:
truncated. You should quit (:q!) and use csplit(1) to divide the
file into smaller pieces.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to edit a file that has 33k+ records. In this file I need to edit each record that has a 'Y' in the 107th position and change the 10 fields before the 'Y' to blanks. Not all records have a 'Y' in the 107th field.
ex:
... (8 Replies)
Discussion started by: jxh461
8 Replies
2. UNIX for Dummies Questions & Answers
Here's what I have...
$ vi foo1
- open foo1 and work around for a while. I yank a few lines into a buffer and then :w to save.
Next I :e foo2 to open foo2 and paste my buffer. I :w to save, but I would like to then be able to go directly back into foo1 where I was before I opened foo2. ... (4 Replies)
Discussion started by: djschmitt
4 Replies
3. Shell Programming and Scripting
hi All,
Plz let me know how to edit a file with 2000000 records.
each record contains with 40 field seperated by |.
i want modify 455487 record, but i am uable to edit this large file using vi editor in unix.
plz let me know how to modify this file.
Thanks in advance.
-Bali Reddy (3 Replies)
Discussion started by: balireddy_77
3 Replies
4. Shell Programming and Scripting
:confused:Folks,
I have a file with 50 million records having 2 columns. I have to do the below:
1. Generate some random numbers of a fixed length.
2. Replace the second column of randomly chosen rows with the random numbers.
I tried using a little bit of perl to generate random numbers... (6 Replies)
Discussion started by: mvijayv
6 Replies
5. Shell Programming and Scripting
Hi,
I need to make a script to edit a file. File is a large file in below format
Version: 2008120101
;$INCLUDE ./abc/xyz/Delhi
;$INCLUDE ./abc/xyz/London
$INCLUDE ./abc/xyz/New York
First line in the file is version number which is in year,month,date and serial number format. Each... (5 Replies)
Discussion started by: makkar4u
5 Replies
6. Shell Programming and Scripting
Hello everyone!
I have 2 types of files in the following format:
1) *.fa
>1234
...some text...
>2345
...some text...
>3456
...some text...
.
.
.
.
2) *.info
>1234 (7 Replies)
Discussion started by: ad23
7 Replies
7. Solaris
Hello everyone. Need some help copying a filesystem. The situation is this: I have an oracle DB mounted on /u01 and need to copy it to /u02. /u01 is 500 Gb and /u02 is 300 Gb. The size used on /u01 is 187 Gb. This is running on solaris 9 and both filesystems are UFS.
I have tried to do it using:... (14 Replies)
Discussion started by: dragonov7
14 Replies
8. UNIX for Dummies Questions & Answers
Hi, sometimes one wants to edit files while still seeing output of earlier commands in terminal. I've found out that cat test && cat - >> test does the trick for displaying file content and adding lines but I believe I saw a much cooler command that was also able to erase lines from files. I cannot... (6 Replies)
Discussion started by: scarleo
6 Replies
9. Shell Programming and Scripting
Whenever I am trying to edit a file in unix with vi editor, I am getting the following error:
<data>
:Tmp file too large
Is there any way that I can edit the file other than vi. Any help is really appreciated.
Thanks (10 Replies)
Discussion started by: bobby1015
10 Replies
10. Shell Programming and Scripting
Experts - I have an requirement to gunzip and edit many files in a pair of directories.
I have two scripts that work great when run separately, but I'm having problems
combining the two.
The goal is to gunzip the files found in the first script and pipe them to the
bash/sed script and... (9 Replies)
Discussion started by: timj123
9 Replies
VIPW(8) BSD System Manager's Manual VIPW(8)
NAME
vipw -- edit the password file
SYNOPSIS
vipw [-d directory]
DESCRIPTION
The vipw utility edits the password file after setting the appropriate locks, and does any necessary processing after the password file is
unlocked. If the password file is already locked for editing by another user, vipw will ask you to try again later. The default editor for
vipw is vi(1).
When run without options, vipw will work with the password files in /etc. The -d option may be used to specify an alternative directory to
work with.
The vipw utility performs a number of consistency checks on the password entries, and will not allow a password file with a ``mangled'' entry
to be installed. If vipw rejects the new password file, the user is prompted to re-enter the edit session.
Once the information has been verified, vipw uses pwd_mkdb(8) to update the user database. This is run in the background, and, at very large
sites could take several minutes. Until this update is completed, the password file is unavailable for other updates and the new information
is not available to programs.
ENVIRONMENT
If the following environment variable exists it will be utilized by vipw:
EDITOR The editor specified by the string EDITOR will be invoked instead of the default editor vi(1). This can be used to allow a
script to non-interactively modify the password file.
PW_SCAN_BIG_IDS See pwd_mkdb(8).
SEE ALSO
chpass(1), passwd(1), passwd(5), adduser(8), pw(8), pwd_mkdb(8)
HISTORY
The vipw utility appeared in 4.0BSD.
BUGS
The mechanism for checking for password file modifications requires that the modification time of the password file changes. This means that
in a default configuration where file system timestamps are not calculated with sub-second precision, EDITOR has to run for at least one sec-
ond. Non-interactive editor scripts should invoke sleep(1) or equivalent to ensure this happens.
BSD
February 14, 2012 BSD