Thanks Jim. I was thinking it might be as difficult as you say. When I've posted the complete situation over the past few days, I get responses that suggest I should not want to know this or do this. As an enthusiast I like to explore and learn, so thought I would try to ask a much more direct technical question to avoid being scolded. :-)
Attached are several of my posts from a more thorough thread I started last week that might answer any questions you have. Sorry it is so long.
I've had these similar data errors on a MacBook 2006 10.6.8, a MacBook 2010 10.8.x, and a two week old MacBook Pro 10.10.5. The older ones have been cleaned up with install of OS. Because of our hack history here I was trying to learn more about this.
The purpose of those comands are to find the newest file in a directory acvrdind to system date, and it has to be recursively found in each directory.
The problem is that i want to list in a long format every found file, but the commands i use produce unexpected results ,so the output lists in a... (5 Replies)
Hi ,
I have a typical situation. I have 4 files and with different headers (number of headers is varible ).
I need to make such a merged file which will have headers combined from all files (comman coluns should appear once only).
For example -
File 1
H1|H2|H3|H4
11|12|13|14
21|22|23|23... (1 Reply)
I have to find the specific formatted file is present in the received list in the directory, for which I have written:
file_list=`ls -lrt /tmp/vinay/act/files |grep "$cdate"| awk '{print $9}'`
while read fileStr
do
find $file_list $fileStr > /dev/null
status=`echo $?`
if ; then
... (3 Replies)
Hi All,
We are copying all the files into ARCHIVE directory after we process them. We are doing this process from last 2 years, now we have a lot of files in ARCHIVE directory.
Now I need to find when the first file is copied into this directory?
If I Issue,
ls -l /ARCHIVE/*.* | tail -1... (3 Replies)
I have an issue with a korn shell script that I am writing. The script parses through a configuration file which lists a heap of path/directories for some files which need to be FTP'd. Now the script needs to check whether there are any files which have not been processed and are X minutes old.
... (2 Replies)
Hi ,
I have a .txt file in which I have multiple headers, the header record starts with $ symbol...like the first column name is $Account.
I have to keep the header in the first line and delete all the remaining headers which are in the file.
I tried using sort adc.txt | uniq -u , but my... (7 Replies)
Hi I need to merge 4 files. The issue i am facing is all the files have headers and i do not want them in the final output file. Can anybody suggest how to do it? (5 Replies)
Hi All,
In the file names we have dates.
Based on the file format given by the user,
if any file is not existed for a particular date with in a given interval we should consider that file is missing.
I have the below files in the directory /bin/daily/voda_files.
... (9 Replies)
Discussion started by: nalu
9 Replies
LEARN ABOUT OSX
nl
NL(1) BSD General Commands Manual NL(1)NAME
nl -- line numbering filter
SYNOPSIS
nl [-p] [-b type] [-d delim] [-f type] [-h type] [-i incr] [-l num] [-n format] [-s sep] [-v startnum] [-w width] [file]
DESCRIPTION
The nl utility reads lines from the named file or the standard input if the file argument is ommitted, applies a configurable line numbering
filter operation and writes the result to the standard output.
The nl utility treats the text it reads in terms of logical pages. Unless specified otherwise, line numbering is reset at the start of each
logical page. A logical page consists of a header, a body and a footer section; empty sections are valid. Different line numbering options
are independently available for header, body and footer sections.
The starts of logical page sections are signalled by input lines containing nothing but one of the following sequences of delimiter charac-
ters:
Line Start of
::: header
:: body
: footer
If the input does not contain any logical page section signalling directives, the text being read is assumed to consist of a single logical
page body.
The following options are available:
-b type Specify the logical page body lines to be numbered. Recognized type arguments are:
a Number all lines.
t Number only non-empty lines.
n No line numbering.
pexpr Number only those lines that contain the basic regular expression specified by expr.
The default type for logical page body lines is t.
-d delim Specify the delimiter characters used to indicate the start of a logical page section in the input file. At most two characters
may be specified; if only one character is specified, the first character is replaced and the second character remains
unchanged. The default delim characters are ``:''.
-f type Specify the same as -b type except for logical page footer lines. The default type for logical page footer lines is n.
-h type Specify the same as -b type except for logical page header lines. The default type for logical page header lines is n.
-i incr Specify the increment value used to number logical page lines. The default incr value is 1.
-l num If numbering of all lines is specified for the current logical section using the corresponding -b a, -f a or -h a option, spec-
ify the number of adjacent blank lines to be considered as one. For example, -l 2 results in only the second adjacent blank
line being numbered. The default num value is 1.
-n format Specify the line numbering output format. Recognized format arguments are:
ln Left justified.
rn Right justified, leading zeros suppressed.
rz Right justified, leading zeros kept.
The default format is rn.
-p Specify that line numbering should not be restarted at logical page delimiters.
-s sep Specify the characters used in separating the line number and the corresponding text line. The default sep setting is a single
tab character.
-v startnum Specify the initial value used to number logical page lines; see also the description of the -p option. The default startnum
value is 1.
-w width Specify the number of characters to be occupied by the line number; in case the width is insufficient to hold the line number,
it will be truncated to its width least significant digits. The default width is 6.
ENVIRONMENT
The LANG, LC_ALL, LC_CTYPE and LC_COLLATE environment variables affect the execution of nl as described in environ(7).
EXIT STATUS
The nl utility exits 0 on success, and >0 if an error occurs.
SEE ALSO jot(1), pr(1)STANDARDS
The nl utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The nl utility first appeared in AT&T System V Release 2 UNIX.
BUGS
Input lines are limited to LINE_MAX (2048) bytes in length.
BSD January 26, 2005 BSD