Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Insert a line of text on nth line of a file Post 302967454 by Don Cragun on Wednesday 24th of February 2016 02:55:07 AM
Old 02-24-2016
You might also want to try the following:
Code:
#!/bin/ksh
dir='/path/of/directory/to/process'
IAm=${0##*/}
tmpf="$IAm.$$"

trap 'rm -f "$tmpf"' EXIT

cd "$dir"
for file in *
do	[ ! -f "$file" ] && continue
	/usr/xpg4/bin/sed '13a\
this is the 14th line
	' "$file" > "$tmpf" && cp "$tmpf" "$file"
done

Obviously, you'll need to change the path shown in red to a path naming the directory in which you want to process your files.

If sed fails for some reason, it won't destroy the file you were trying to update (which RavinderSingh13's suggestion might do if the awk fails).

If there are any hard links to any of the files being processed, this script will maintain those links. (The code RavinderSingh13 suggested will break the links, if there are any, creating two separate (unlinked) files.)

This would probably also work with /usr/bin/sed on Solaris systems, but I'm almost positive it will work with /usr/xpg4/bin/sed. Unfortunately, I don't have a Solaris system available for testing.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Insert text file at a certain line.

I need to insert a file called temp_impact (which has about 15 lines in it) to a file called 11.23cfg starting at line 33. I searched the forums and found the sed '34i\ test' 11.23cfg > newfile That will enter word test at the appropriate line, but i need the entire file dumped there. Any... (4 Replies)
Discussion started by: insania
4 Replies

2. Shell Programming and Scripting

how to insert a extra line in a text file

how to insert a extra line in a text file using a sh command iam trying to think of a way to add a extra line but without deleting the whole text do anyone have any ideas (2 Replies)
Discussion started by: bhaviknp
2 Replies

3. Shell Programming and Scripting

Insert a line in a text file

So I need to write lines into line X of file X. I can get the file by doing: cfgnumber=$(cat -n -comm.cfg| grep -i "servicegroup_name 24x7-comunicacions") echo $cfgnumber it outputs the Line where it finds now I need to start writing something right bellow that line. thanks (10 Replies)
Discussion started by: 4scriptmoni
10 Replies

4. Shell Programming and Scripting

How to insert some constant text at beginig of each line within a text file.

Dear Folks :), I am new to UNIX scripting and I do not know how can I insert some text in the first column of a UNIX text file at command promtp. I can do this in vi editor by using this command :g/^/s//BBB_ e,g I have a file named as Test.dat and it containins below text: michal... (4 Replies)
Discussion started by: Muhammad Afzal
4 Replies

5. Shell Programming and Scripting

Using sed to insert text file at first line

sed '1r file.txt' <source.txt >desti.txt This example will insert 'file.txt' between line 1 and 2 of source.txt. sed '0r file.txt' <source.txt >desti.txt gives an error message. Does anyone know how 'sed' can insert 'file.txt' before the first line of source.txt? (18 Replies)
Discussion started by: psve
18 Replies

6. UNIX for Dummies Questions & Answers

Insert a line in a sorted text file(s)

Hello, I am trying to add a line (usually just a word) to some text files in a directory that are already sorted. I just don't want to run the sort command again because it can take a long time when the text or log files are really huge. I have a bashscript that will take in the 1st argument... (7 Replies)
Discussion started by: raptor25
7 Replies

7. Shell Programming and Scripting

How to start reading from the nth line till the last line of a file.

Hi, For my reuirement, I have to read a file from the 2nd line till the last line<EOF>. Say, I have a file as test.txt, which as a header record in the first line followed by records in rest of the lines. for i in `cat test.txt` { echo $i } While doing the above loop, I have read... (5 Replies)
Discussion started by: machomaddy
5 Replies

8. UNIX for Dummies Questions & Answers

Insert a line in a text file

I want to insert a line with text after the 9th line of a text file. How would I do this using sed or awk? (2 Replies)
Discussion started by: lost.identity
2 Replies

9. Shell Programming and Scripting

How to read a text file line by line and insert into a database table?

I have a test file that I want to read and insert only certain lines into the the table based on a filter. 1. Rread the log file 12 Hours back Getdate() -12 Hours 2. Extract the following information on for lines that say "DUMP is complete" A. Date B. Database Name C.... (2 Replies)
Discussion started by: JolietJake
2 Replies

10. Shell Programming and Scripting

Printing string from last field of the nth line of file to start (or end) of each line (awk I think)

My file (the output of an experiment) starts off looking like this, _____________________________________________________________ Subjects incorporated to date: 001 Data file started on machine PKSHS260-05CP ********************************************************************** Subject 1,... (9 Replies)
Discussion started by: samonl
9 Replies
ln(1)								   User Commands							     ln(1)

NAME
ln - make hard or symbolic links to files SYNOPSIS
/usr/bin/ln [-fns] source_file [target] /usr/bin/ln [-fns] source_file... target /usr/xpg4/bin/ln [-fs] source_file [target] /usr/xpg4/bin/ln [-fs] source_file... target DESCRIPTION
In the first synopsis form, the ln utility creates a new directory entry (link) for the file specified by source_file, at the destination path specified by target. If target is not specified, the link is made in the current directory. This first synopsis form is assumed when the final operand does not name an existing directory; if more than two operands are specified and the final is not an existing directory, an error will result. In the second synopsis form, the ln utility creates a new directory entry for each file specified by a source_file operand, at a destina- tion path in the existing directory named by target. The ln utility may be used to create both hard links and symbolic links. A hard link is a pointer to a file and is indistinguishable from the original directory entry. Any changes to a file are effective independent of the name used to reference the file. Hard links may not span file systems and may not refer to directories. ln by default creates hard links. source_file is linked to target. If target is a directory, another file named source_file is created in target and linked to the original source_file. If target is an existing file and the -f option is not specified, ln will write a diagnostic message to standard error, do nothing more with the current source_file, and go on to any remaining source_files. A symbolic link is an indirect pointer to a file; its directory entry contains the name of the file to which it is linked. Symbolic links may span file systems and may refer to directories. File permissions for target may be different from those displayed with an -l listing of the ls(1) command. To display the permissions of target, use ls -lL. See stat(2) for more information. /usr/bin/ln If /usr/bin/ln determines that the mode of target forbids writing, it prints the mode (see chmod(1)), asks for a response, and reads the standard input for one line. If the response is affirmative, the link occurs, if permissible. Otherwise, the command exits. /usr/xpg4/bin/ln When creating a hard link, and the source file is itself a symbolic link, the target will be a hard link to the file referenced by the sym- bolic link, not to the symbolic link object itself (source_file). OPTIONS
The following options are supported for both /usr/bin/ln and /usr/xpg4/bin/ln: -f Links files without questioning the user, even if the mode of target forbids writing. This is the default if the standard input is not a terminal. -s Creates a symbolic link. If the -s option is used with two arguments, target may be an existing directory or a non-existent file. If target already exists and is not a directory, an error is returned. source_file may be any path name and need not exist. If it exists, it may be a file or directory and may reside on a different file system from target. If target is an existing directory, a file is created in directory target whose name is source_file or the last component of source_file. This file is a symbolic link that references source_file. If target does not exist, a file with name target is created and it is a symbolic link that references source_file. If the -s option is used with more than two arguments, target must be an existing directory or an error will be returned. For each source_file, a link is created in target whose name is the last component of source_file. Each new source_file is a symbolic link to the original source_file. The files and target may reside on different file systems. /usr/bin/ln The following option is supported for /usr/bin/ln only: -n If target is an existing file, writes a diagnostic message to stderr and goes on to any remaining source_files. The -f option overrides this option. This is the default behavior for /usr/bin/ln and /usr/xpg4/bin/ln, and is silently ignored. OPERANDS
The following operands are supported: source_file A path name of a file to be linked. This can be either a regular or special file. If the -s option is specified, source_file can also be a directory. target The path name of the new directory entry to be created, or of an existing directory in which the new directory entries are to be created. USAGE
See largefile(5) for the description of the behavior of ln when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes). ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of ln: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 All the specified files were linked successfully >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/ln +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ /usr/xpg4/bin/ln +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWxcu4 | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
chmod(1), ls(1), stat(2), attributes(5), environ(5), largefile(5), standards(5) NOTES
A symbolic link to a directory behaves differently than you might expect in certain cases. While an ls(1) command on such a link displays the files in the pointed-to directory, entering ls -l displays information about the link itself: example% ln -s dir link example% ls link file1 file2 file3 file4 example% ls -l link lrwxrwxrwx 1 user 7 Jan 11 23:27 link -> dir When you change to a directory (see cd(1)) through a symbolic link, using /usr/bin/sh or /usr/bin/csh, you wind up in the pointed-to loca- tion within the file system. This means that the parent of the new working directory is not the parent of the symbolic link, but rather, the parent of the pointed-to directory. This will also happen when using cd with the -P option from /usr/bin/ksh or /usr/xpg4/bin/sh. For instance, in the following case, the final working directory is /usr and not /home/user/linktest. example% pwd /home/user/linktest example% ln -s /usr/tmp symlink example% cd symlink example% cd .. example% pwd /usr C shell users can avoid any resulting navigation problems by using the pushd and popd built-in commands instead of cd. SunOS 5.10 25 Mar 2004 ln(1)
All times are GMT -4. The time now is 02:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy