Reading a file line by line and processing for each line

02-27-2009

Registered User

123, 3

Join Date: Sep 2007

Last Activity: 12 August 2010, 12:56 PM EDT

Location: Poland

Posts: 123

Thanks Given: 2

Thanked 3 Times in 3 Posts

Beginner? This is one of the better ksh codes that I have seen. And believe me - I have seen plenty od it.
Some hints that might help you:
- Try enclosing variables with quotes: variable="${var}" (the way you are using could work fine but under some circumstances you can get into problems - an example is when ${var} is equal to 'some text with $trange characters').
- I'm not sure if there is a need to enclose that function within brackets - if I remember correct you should be able to "print" the file into the loop without brackets
- Send this sid_home.txt file and make sure that the problem is not related to end of line characters (unix/max/windows format) - if you send it then I could take a look onto it
- Use tabulation - this code you have sent is not very readable
- You might try the alternative syntax as well (might be worth giving a try): cat "${file}" | while $(read LINE);do ... done
- Execute your code with "set -x;set -v" and check the output. You might try some debuggers as well.

adderek

View Public Profile for adderek

Find all posts by adderek

exit(1) User Commands exit(1) NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps SYNOPSIS
sh exit [n] return [n] csh exit [ ( expr )] goto label ksh *exit [n] *return [n] DESCRIPTION
sh exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of the last command executed (an EOF will also cause the shell to exit.) return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe- cuted. csh exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the expression expr. The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to jump to a label that occurs between a while or for built-in command and its corresponding end. ksh exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8 bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit except for a shell which has the ignoreeof option (See set below) turned on. return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return is invoked while not in a function or a '.' script, then it is the same as an exit. On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5) SunOS 5.10 15 Apr 1994 exit(1)

Shell Programming and Scripting

Reading a file line by line and processing for each line

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Reading a file line by line and print required lines based on pattern

Discussion started by: balu1234

2. Shell Programming and Scripting

Reading line by line from live log file using while loop and considering only those lines start from

Discussion started by: ketanraut

3. Shell Programming and Scripting

Comparison of fields then increment a counter reading line by line in a file

Discussion started by: selvankj

4. Shell Programming and Scripting

Reading text file, comparing a value in a line, and placing only part of the line in a variable?

Discussion started by: xChristopher

5. Shell Programming and Scripting

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

Discussion started by: machomaddy

6. UNIX for Dummies Questions & Answers

Parsing file, reading each line to variable, evaluating date/time stamp of each line

Discussion started by: hynesward

7. Shell Programming and Scripting

[Solved] Problem in reading a file line by line till it reaches a white line

Discussion started by: hakermania

8. Shell Programming and Scripting

reading a file inside awk and processing line by line

Discussion started by: Anteus

9. Shell Programming and Scripting

KSH: Reading a file line by line into multiple arrays

Discussion started by: sniper57

LEARN ABOUT SUNOS

return