uniq - report or filter out repeated lines in a file
uniq [-c|-d|-u][-f fields][-s char][input_file [output_file]]
The uniq utility shall read an input file comparing adjacent lines, and write one copy of each input line on the output. The second and succeeding copies of repeated adjacent input lines shall not be written.
Repeated lines in the input shall not be detected if they are not adjacent.
The uniq utility shall conform to the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
The following options shall be supported:
[[:blank:]]*[^[:blank:]]*
If the fields option-argument specifies more fields than appear on an input line, a null string shall be used for comparison.
The following operands shall be supported:
The standard input shall be used only if no input_file operand is specified or if input_file is '-' . See the INPUT FILES section.
The input file shall be a text file.
The following environment variables shall affect the execution of uniq:
Determine the locale for ordering rules.
The standard output shall be used only if no output_file operand is specified. See the OUTPUT FILES section.
The standard error shall be used only for diagnostic messages.
If the -c option is specified, the output file shall be empty or each line shall be of the form:
"%d %s", <number of duplicates>, <line>
otherwise, the output file shall be empty or each line shall be of the form:
"%s", <line>
The following exit values shall be returned:
Default.
The following sections are informative.
The sort utility can be used to cause repeated lines to be adjacent in the input file.
The following input file data (but flushed left) was used for a test series on uniq:
#01 foo0 bar0 foo1 bar1 #02 bar0 foo1 bar1 foo1 #03 foo0 bar0 foo1 bar1 #04 #05 foo0 bar0 foo1 bar1 #06 foo0 bar0 foo1 bar1 #07 bar0 foo1 bar1 foo0
What follows is a series of test invocations of the uniq utility that use a mixture of uniq options against the input file data. These tests verify the meaning of adjacent. The uniq utility views the input data as a sequence of strings delimited by '\n' . Accordingly, for the fieldsth member of the sequence, uniq interprets unique or repeated adjacent lines strictly relative to the fields+1th member.
This first example tests the line counting option, comparing each line of the input file data starting from the second field:
uniq -c -f 1 uniq_0I.t 1 #01 foo0 bar0 foo1 bar1 1 #02 bar0 foo1 bar1 foo0 1 #03 foo0 bar0 foo1 bar1 1 #04 2 #05 foo0 bar0 foo1 bar1 1 #07 bar0 foo1 bar1 foo0
The number '2' , prefixing the fifth line of output, signifies that the uniq utility detected a pair of repeated lines. Given the input data, this can only be true when uniq is run using the -f 1 option (which shall cause uniq to ignore the first field on each input line).
The second example tests the option to suppress unique lines, comparing each line of the input file data starting from the second field:
uniq -d -f 1 uniq_0I.t #05 foo0 bar0 foo1 bar1
This test suppresses repeated lines, comparing each line of the input file data starting from the second field:
uniq -u -f 1 uniq_0I.t #01 foo0 bar0 foo1 bar1 #02 bar0 foo1 bar1 foo1 #03 foo0 bar0 foo1 bar1 #04 #07 bar0 foo1 bar1 foo0
This suppresses unique lines, comparing each line of the input file data starting from the third character:
uniq -d -s 2 uniq_0I.t
In the last example, the uniq utility found no input matching the above criteria.
Some historical implementations have limited lines to be 1080 bytes in length, which does not meet the implied {LINE_MAX} limit.
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |