Obviously it will come because you have set field separator as [[:space:]],(writing like [[:space:]] as with comma space is not coming into iCode tags here) and it couldn't find any field as NF-2 so thus giving an error because it is taking it as a single field.
Could you please try following and let me know if this helps you.
Code:
uptime | awk -F'[ ,]' '{print $(NF-4)}'
If you need to know how fields are getting acquired then you could run following command too.
Hi I have a process generating a file in Solaris. Now we have migrated the process to Linux. When we open the file in vi on solaris and hit space bar, it stops after reaching the end of line. But in linux it continues to go on the next line. So I want to know whether the difference is between the... (4 Replies)
Hi,
I am issuing find command below mentioned ways but it givs different count. I don't understand the behaviour. Could any one have any clue?
$ find . -mtime -5 -maxdepth 1 -exec ls -lrt {} \; | wc -l
169
$ find . -mtime -5 -maxdepth 1 | wc -l
47
$ find . -mtime -5 -maxdepth 1 | wc -l... (2 Replies)
I ran one the script in debug mode in linux and have a problem
ret='$prmAttunityUser=ais'
Now i need to remove $ from this '$prmAttunityUser=ais' so i had added a sed command like this sed 's/$//g' but its not working could you all please help me with an alternate command
I want the output... (3 Replies)
Hi,
awk -v is having issue in sun solaris, however the same works fine in HP Superdome. Pls advise what to do, while executing below command in SunOS.
echo "this is saurabh"|awk -v a="SAURABH" '{ print a }' (2 Replies)
Hi,
:wall:
I am not able to run any utility command in Redat, Please see the below example and suggest me how I shall run this type of command.
$ su
Password:
# ifconfig
bash: ifconfig: command not found
# which ifconfig
/usr/bin/which: no ifconfig in... (3 Replies)
Hello Gurus,
I am trying to set up bidirectional password-less login between a linux and a Solaris. The way I am doing is very simple, which is creating pub/priv key pairs on each host and add the pub key to each other's authorized_keys file:
ssh-keygen -t rsa (I tried dsa, and it didn't work... (4 Replies)
Hi All,
I am using the below script which has awk command, but it is not returing the expected result. can some pls help me to correct the command.
The below script sample.ksh should give the result if the value of last 4 digits in the variable NM matches with the variable value DAT. The... (7 Replies)
Hi ,
I am trying to execute the below command, i got error msg..
Please advice me how to solve this
See, When i raised psr cmd., then i got error like above ,
Please help on this
THanks
Mani (0 Replies)
Hello,
I am on a Mac and trying to clean up some monthly files with a very simple SED:
sed '3,10d;/<ACROSS>/,$d' input.txt > output.txt
(from the input, delete lines 3 - 10; then delete from the line containing <ACROSS> to the end of the file)
then output to output.txt
Even when I try... (2 Replies)
Discussion started by: verbatim
2 Replies
LEARN ABOUT FREEBSD
join
JOIN(1) BSD General Commands Manual JOIN(1)NAME
join -- relational database operator
SYNOPSIS
join [-a file_number | -v file_number] [-e string] [-o list] [-t char] [-1 field] [-2 field] file1 file2
DESCRIPTION
The join utility performs an ``equality join'' on the specified files and writes the result to the standard output. The ``join field'' is
the field in each file by which the files are compared. The first field in each line is used by default. There is one line in the output
for each pair of lines in file1 and file2 which have identical join fields. Each output line consists of the join field, the remaining
fields from file1 and then the remaining fields from file2.
The default field separators are tab and space characters. In this case, multiple tabs and spaces count as a single field separator, and
leading tabs and spaces are ignored. The default output field separator is a single space character.
Many of the options use file and field numbers. Both file numbers and field numbers are 1 based, i.e., the first file on the command line is
file number 1 and the first field is field number 1. The following options are available:
-a file_number
In addition to the default output, produce a line for each unpairable line in file file_number.
-e string
Replace empty output fields with string.
-o list
The -o option specifies the fields that will be output from each file for each line with matching join fields. Each element of list
has either the form file_number.field, where file_number is a file number and field is a field number, or the form '0' (zero), repre-
senting the join field. The elements of list must be either comma (',') or whitespace separated. (The latter requires quoting to
protect it from the shell, or, a simpler approach is to use multiple -o options.)
-t char
Use character char as a field delimiter for both input and output. Every occurrence of char in a line is significant.
-v file_number
Do not display the default output, but display a line for each unpairable line in file file_number. The options -v 1 and -v 2 may be
specified at the same time.
-1 field
Join on the field'th field of file1.
-2 field
Join on the field'th field of file2.
When the default field delimiter characters are used, the files to be joined should be ordered in the collating sequence of sort(1), using
the -b option, on the fields on which they are to be joined, otherwise join may not report all field matches. When the field delimiter char-
acters are specified by the -t option, the collating sequence should be the same as sort(1) without the -b option.
If one of the arguments file1 or file2 is '-', the standard input is used.
EXIT STATUS
The join utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
For compatibility with historic versions of join, the following options are available:
-a In addition to the default output, produce a line for each unpairable line in both file1 and file2.
-j1 field
Join on the field'th field of file1.
-j2 field
Join on the field'th field of file2.
-j field
Join on the field'th field of both file1 and file2.
-o list ...
Historical implementations of join permitted multiple arguments to the -o option. These arguments were of the form
file_number.field_number as described for the current -o option. This has obvious difficulties in the presence of files named 1.2.
These options are available only so historic shell scripts do not require modification and should not be used.
SEE ALSO awk(1), comm(1), paste(1), sort(1), uniq(1)STANDARDS
The join command conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
BSD July 5, 2004 BSD