04-22-2008
neither worked!!
In both cases it hangs, looks like some syntax issue. any further suggestions!!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a requirement to search for a string in a large log file along with few lines before and after the the string. The following script was sufficient to search such an entry.
STRING_TO_GREP="$1"
FILE_TO_GREP="$2"
NUMBER_OF_LINES_BEFORE=$3
NUMBER_OF_LINES_AFTER=$4
for i in `grep... (3 Replies)
Discussion started by: praveen123
3 Replies
2. Shell Programming and Scripting
Hello,
I've searched through the scripting section but could not find what I need.
I need to search for empty sections within a file and remove them.
Here is an example file:
Title 123
A
B
C
D
E
Title 098
Title 567
Z
Y (4 Replies)
Discussion started by: leepet01
4 Replies
3. Shell Programming and Scripting
Hi,
I have a file like this
comment.txt
1.img
2.img
3.img
OK
x.img
y.img
z.img
not ok
1.img
2.img
3.img
bad
1.img
2.img
3.img (7 Replies)
Discussion started by: avatar_007
7 Replies
4. UNIX for Dummies Questions & Answers
I am trying to search for lines present in file a that do not exist in file b and print out the lines. E.g.
file a
apple
pear
banana
orange
file b
apple
banana
orange
would output to stdout: pear.
... (3 Replies)
Discussion started by: thurmc
3 Replies
5. Shell Programming and Scripting
Hi, i would really appreciate any help anyone can give with the following info.
Thanks in advance.
I need to run a search on a file that contains thousands of trades, each trade is added into the file in blocks of 25 lines. i know the search has to take place between a time stamp specified... (4 Replies)
Discussion started by: sp3arsy
4 Replies
6. Shell Programming and Scripting
Hi,
I am new to shell scripting and is working on a script to extract lines from a log file between two time stamps using awk command. After some research I used following command:
awk '/01 Oct 2011/{p=1} /10 Oct 2011/{p=0} p' test.log >> tmp.log
This works fine. But now i want to... (3 Replies)
Discussion started by: davidtd
3 Replies
7. Shell Programming and Scripting
HI group members
I am new in unix
I want to search # symbol in a file.
if found need to delete the entire row in the file.
need to move the actual data(with out # symbol data) to another file.
Thanks (2 Replies)
Discussion started by: pmreddy
2 Replies
8. Shell Programming and Scripting
I have a log file where every line starts with a time stamp. I have to extract lines from the file within a given time stamp.
For example:
IF the file is like this:
2012-08-19 10:34:03,446|WebContainer : 56|OrderHeaderDaoImpl|findByKeys|26|
2012-08-20 11:34:03,463|WebContainer :... (8 Replies)
Discussion started by: abhinalluri
8 Replies
9. Shell Programming and Scripting
Hello,
I want to search 2 lines from the file. I wanted to display all such matches. Example file:
==================
Testfile is test
TEST1
TEST2
testing the file string
to do testing
TEST1
TEST2
sample strings
=================
I wanted to search the file with 2 lines
"
TEST1... (3 Replies)
Discussion started by: balareddy
3 Replies
10. Shell Programming and Scripting
Hi,
I want to pull lines between two timestamps from a file. When I just insert values directly it is working fine.
sed -n '/2014-02-14 05:30/,/2014-02-14 05:31/p' Logfile
When I try to insert variable it is not working.
sed -n '/TZ=GMT+1 date +%Y-%m-%d" "%H:%M:%S/,/TZ=GMT date... (2 Replies)
Discussion started by: Neethu
2 Replies
LEARN ABOUT NETBSD
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)