03-22-2015
FNR>1 FNR==NR is not a valid awk conditional expression. If you're trying to select all lines in the 1st input file except for the 1st line in that file, you want something like: FNR>1 && FNR==NR.
10 More Discussions You Might Find Interesting
1. Solaris
I'm new in Solaris server
After the system support reboot the Solaris server, all the files in /tmp has been removed, is that normal under Solaris or under different init level will get different result?
which init level will do that? (5 Replies)
Discussion started by: yesthomas
5 Replies
2. Shell Programming and Scripting
Please help. Here is my problem. I have 9000 lines in file a and 500,000 lines in file b. For each line in file a I need to search file b and remove that line. I am currently using the grep -v command and loading the output into a new file. However, because of the size of file b this takes an... (4 Replies)
Discussion started by: mjs3221
4 Replies
3. UNIX for Dummies Questions & Answers
Hi,
How do we remove an extra new line in a file. New line in ascii is called chr(10). Suppose we have a file as:
12345
98765
------
------
From the above i represented new line with dashed lines. Basically i have 2 new lines with white space at the end of the file. How do i removes... (1 Reply)
Discussion started by: sandeep_1105
1 Replies
4. Linux
Hi Team,
I have deleted a file accidentally by using rm command. I am not the root(admin) user. Can you please let me know how to get that .tex file? (2 Replies)
Discussion started by: darling
2 Replies
5. Red Hat
For Suppose, I have installed a package having files file1, file2 and file3. After installation, I removed the file "file3".
But "rpm -qf file3" is giving the package name, even file3 was not there. And also "rpm -ql package" is also displaying all 3 files.
How can i update rpm database about... (6 Replies)
Discussion started by: snreddy_gopu
6 Replies
6. Programming
The fwrite function call is not returning error, when the file it writes to is removed, please advise on how to find if the file already opened and being written by a program is removed manually or by some other process.
please see the code below,
#include<stdio.h>
#include<stdlib.h>
... (3 Replies)
Discussion started by: Kesavan
3 Replies
7. Solaris
Does anyone have any advise on trying to clean up a full filesystem? I can't rm any files because of the follow:
not removed: No space left on device
Any help would be very much appreciated. (10 Replies)
Discussion started by: craigsky
10 Replies
8. UNIX for Beginners Questions & Answers
The input file is this:
a|b|c|d
x|y|z|n|||||||||
p|q|r|s|||
g|h|i|
w|e|r||
Now as per requirement , each row should have only 3 delimiter.
Now the 2nd row & last row has an extra delimiter, How to remove that ? In some large file having 100K data , there can be 100 such rows having... (4 Replies)
Discussion started by: ikdKunal
4 Replies
9. UNIX for Beginners Questions & Answers
Hi Folks,
I have a requirement of file management on different servers.
Source Server is SERVER-A.
Two servers will fetch files from SERVER-A: SERVER1 and SERVER2.
4th SERVER is SERVER-B, It will fetch files from SERVER1. If SERVER1 goes DOWN, SERVER-B will fetch pending files from... (2 Replies)
Discussion started by: Raza Ali
2 Replies
10. Shell Programming and Scripting
Hi All,
Is there is any machanisim, once delete the file can we restore it.
Thanks (8 Replies)
Discussion started by: bmk123
8 Replies
LEARN ABOUT HPUX
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)
NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS
--help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO
lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities CHECKBASHISMS(1)