7:11 p.m.
Hello all,
I have a weather server which shoots out National Weather Service
bulletins to me when they have certain keywords. For instance:
#!/bin/sh
dir=/blah/blah
/bin/cat <&0 > ${dir}$1.$$
if [ `/bin/grep -- " IL " ${dir}$1.$$ | /usr/bin/wc -l` -gt 0 ]
then
/bin/cat ${dir}$1.$$ | /bin/mail -s "ALERT: LOOK OUT!!!" user(a)machine.com
fi
/bin/rm -f ${dir}$1.$$
This script worked in FC1, but not FC3. I suspect a change in the grep
command syntax. But does anyone know for sure before I try to drive myself
nuts trying to figure this out?
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
E-mail: sebenste(a)weather.admin.niu.edu ***
*******************************************************************************
8:14 p.m.
On Sat, Nov 05, 2005 at 07:11:25PM -0600, Gilbert Sebenste wrote:
#!/bin/sh
dir=/blah/blah
/bin/cat <&0 > ${dir}$1.$$
if [ `/bin/grep -- " IL " ${dir}$1.$$ | /usr/bin/wc -l` -gt 0 ]
then
/bin/cat ${dir}$1.$$ | /bin/mail -s "ALERT: LOOK OUT!!!" user(a)machine.com
fi
/bin/rm -f ${dir}$1.$$
Well, for starters, there's a lot of needless complexity with file
descriptors and temporary files in your script. If you can't isolate
the problem, you might try the version I included at the bottom, which
works fine for me on my FC3 system (though yours did too, on the test
input I used). I'll note that you seem to need a '/' as the 1st
character of $1... or else you need to make sure that /blah/blah$1.$$
is a (possibly not yet existing) regular file in /blah to which the
user has write access... i.e. your filename is blah$1.$$ and is in
/blah.
This script worked in FC1, but not FC3. I suspect a change in the
grep
command syntax. But does anyone know for sure before I try to drive myself
nuts trying to figure this out?
That seems rather unlikely... at least not in such a way as to affect
the rather simple grep that you're using. More likely, your input to
the script has changed and you didn't notice (or your real script is
different from the one you posted). Maybe there is not a space
character on either side of the IL that you are trying to match? That
would be my first guess...
If not, maybe you could post some sample input? Or, try this script:
-=-=-=-
#!/bin/sh
foo=`grep -- " IL "`
if [ "$foo" ]; then
echo "$foo" | /bin/mail -s "ALERT: LOOK OUT!!!"
user(a)machine.com
fi
-=-=-=-
This should do what you want without dealing with temp files and
descriptors.
--
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D
12:31 a.m.
On Sat, 5 Nov 2005, Derek Martin wrote:
> #!/bin/sh
> dir=/blah/blah
> /bin/cat <&0 > ${dir}$1.$$
> if [ `/bin/grep -- " IL " ${dir}$1.$$ | /usr/bin/wc -l` -gt 0 ]
> then
> /bin/cat ${dir}$1.$$ | /bin/mail -s "ALERT: LOOK OUT!!!" user(a)machine.com
> fi
> /bin/rm -f ${dir}$1.$$
Well, for starters, there's a lot of needless complexity with file
descriptors and temporary files in your script. If you can't isolate
the problem, you might try the version I included at the bottom, which
works fine for me on my FC3 system (though yours did too, on the test
input I used). I'll note that you seem to need a '/' as the 1st
character of $1... or else you need to make sure that /blah/blah$1.$$
is a (possibly not yet existing) regular file in /blah to which the
user has write access... i.e. your filename is blah$1.$$ and is in
/blah.
I changed the directory for security reasons, obviously, and I forgot to
put a "/" in the last "blah", so it should have read:
dir=/blah/blah/
> This script worked in FC1, but not FC3. I suspect a change in the
grep
> command syntax. But does anyone know for sure before I try to drive myself
> nuts trying to figure this out?
That seems rather unlikely... at least not in such a way as to affect
the rather simple grep that you're using. More likely, your input to
the script has changed and you didn't notice (or your real script is
different from the one you posted). Maybe there is not a space
character on either side of the IL that you are trying to match? That
would be my first guess...
Nope, I have similar scripts for flood warnings, tornado watches,
etc...and they're *all* failing.
If not, maybe you could post some sample input? Or, try this
script:
-=-=-=-
#!/bin/sh
foo=`grep -- " IL "`
if [ "$foo" ]; then
echo "$foo" | /bin/mail -s "ALERT: LOOK OUT!!!"
user(a)machine.com
fi
-=-=-=-
This should do what you want without dealing with temp files and
descriptors.
The problem is, what if I have three descriptors, or maybe 4, AND if there
is a certain word or words in there, then don't send it out?
In a file, it makes it easier.
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste(a)weather.admin.niu.edu ***
web: http://weather.admin.niu.edu **
Work phone: 815-753-5492 *
*******************************************************************************
1:38 a.m.
On Sun, 6 Nov 2005, Gilbert Sebenste wrote:
> That seems rather unlikely... at least not in such a way as to
affect
> the rather simple grep that you're using. More likely, your input to
> the script has changed and you didn't notice (or your real script is
> different from the one you posted). Maybe there is not a space
> character on either side of the IL that you are trying to match? That
> would be my first guess...
I removed the "$1" and it printed the correct file in the /blah/blah
doirectory, but the script failed to spit out an email. Here's the input:
367
WWUS30 KWNS 060329
SAW3
SPC AWW 060329
WW 843 SEVERE TSTM AR IL IN KY MO 060330Z - 061000Z
AXIS..80 STATUTE MILES EAST AND WEST OF LINE..
25S BVX/BATESVILLE AR/ - 50NNW LAF/LAFAYETTE IN/
..AVIATION COORDS.. 70NM E/W /49NNE LIT - 33NNW BVT/
HAIL SURFACE AND ALOFT..1.5 INCHES. WIND GUSTS..70 KNOTS.
MAX TOPS TO 450. MEAN STORM MOTION VECTOR 24035.
REPLACES WW 841..IL MO
REPLACES WW 842..AR MO
THIS IS AN APPROXIMATION TO THE WATCH AREA. FOR A
COMPLETE DEPICTION OF THE WATCH SEE WOUS64 KWNS
FOR WOU3.
It should hit on the first "IL". Can someone try this on FC4 and see what
happens for you?
I still suspect wc or grep changed its options.
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste(a)weather.admin.niu.edu ***
web: http://weather.admin.niu.edu **
Work phone: 815-753-5492 *
*******************************************************************************
10:49 a.m.
On Sun, Nov 06, 2005 at 12:31:49AM -0600, Gilbert Sebenste wrote:
>-=-=-=-
>#!/bin/sh
>foo=`grep -- " IL "`
>if [ "$foo" ]; then
> echo "$foo" | /bin/mail -s "ALERT: LOOK OUT!!!"
user(a)machine.com
>fi
>-=-=-=-
>
>This should do what you want without dealing with temp files and
>descriptors.
The problem is, what if I have three descriptors, or maybe 4, AND if there
is a certain word or words in there, then don't send it out?
In a file, it makes it easier.
Well, I guess so... Without seeing examples of what you mean I can't
really comment one way or the other.
On Sun, Nov 06, 2005 at 01:38:01AM -0600, Gilbert Sebenste wrote:
I removed the "$1" and it printed the correct file in the
/blah/blah
doirectory, but the script failed to spit out an email. Here's the input:
If the file is right, then the grep is fine. If you didn't get mail,
then most likely your sendmail configuration isn't right.
As root, type:
# mailq -Ac
Does it show you any messages waiting? If so, your sendmail
configuration is likely the problem.
It should hit on the first "IL". Can someone try this on
FC4 and see what
happens for you?
I still suspect wc or grep changed its options.
You're not using any options, and the so that really can't possibly be the
problem. The grep and wc utilities are ancient Unix work-alikes;
their syntax hasn't changed substantially in about 30 years, barring
the addition or renaming of a few mostly rather esoteric features. It
really can't; changing the syntax would break 3 decades of code,
probably violate POSIX standards, and definitely irritate a lot of
people. You're barking up the wrong tree here.
--
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D
7:32 a.m.
Gilbert Sebenste wrote:
It should hit on the first "IL". Can someone try this on
FC4 and see what
happens for you?
Works fine here, on FC4 (x86_84). Do you have LANG or LC_* set?
set | grep LANG
set | grep LC_
I understand that the ${dir}$1.$$ file is correctly created: you might
want to have commands after the /bin/mail and before the fi to append
the date, filename and file contents into a log file somewhere. That way
you can be pretty sure that everything is working until the /bin/mail.
As has been pointed out, there are more efficient ways of writing that
shell script. Even if I'd have kept the temp file, I'd probably have
gone for
file=/blah/blah/$1.$$
instead of $dir, and something like
grep -q " IL " $file && mail -s "ALERT: LOOK OUT!"
user(a)example.com < $file
Hope this helps,
James.
--
E-mail address: james | "Today Has Been Two Of Those Days."
@westexe.demon.co.uk | -- Mike Andrews
7:46 a.m.
I wrote:
Works fine here, on FC4 (x86_84). Do you have LANG or LC_* set?
set | grep LANG
set | grep LC_
I understand that the ${dir}$1.$$ file is correctly created: you might
want to have commands after the /bin/mail and before the fi to append
the date, filename and file contents into a log file somewhere. That way
you can be pretty sure that everything is working until the /bin/mail.
You might want to direct the set | grep commands to the log file: that
way you know how the environment is set, and you're not guessing.
Come to that, just
set >> $logfile
Hope this helps,
James.
--
E-mail address: james | "But alas, we don't need a car, so I have a bus
@westexe.demon.co.uk | timetable and one day the buses will read it too."
| -- Telsa Gwynne
12:58 p.m.
On Sat, 5 Nov 2005, Derek Martin wrote:
> This script worked in FC1, but not FC3. I suspect a change in the
grep
> command syntax. But does anyone know for sure before I try to drive myself
> nuts trying to figure this out?
That seems rather unlikely... at least not in such a way as to affect
the rather simple grep that you're using. More likely, your input to
the script has changed and you didn't notice (or your real script is
different from the one you posted). Maybe there is not a space
character on either side of the IL that you are trying to match? That
would be my first guess...
If not, maybe you could post some sample input? Or, try this script:
Here's what I get when I run my script:
Berkeley DB version mismatch: compiled against 4.1.25, run-time linked
against 4.3.27
What the heck does THAT mean?
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste(a)weather.admin.niu.edu ***
web: http://weather.admin.niu.edu **
Work phone: 815-753-5492 *
*******************************************************************************
1:21 p.m.
On Sun, Nov 06, 2005 at 12:58:04PM -0600, Gilbert Sebenste wrote:
Here's what I get when I run my script:
Berkeley DB version mismatch: compiled against 4.1.25, run-time linked
against 4.3.27
What the heck does THAT mean?
Well, the only program you're executing that's linked against Berkely
DB is sendmail (called indirectly by /bin/mail):
$ ldd `which grep`
linux-gate.so.1 => (0x003e5000)
libpcre.so.0 => /lib/libpcre.so.0 (0x0029e000)
libc.so.6 => /lib/tls/libc.so.6 (0x00111000)
/lib/ld-linux.so.2 (0x00321000)
$ ldd /bin/mail
linux-gate.so.1 => (0x00f1e000)
libc.so.6 => /lib/tls/libc.so.6 (0x0033b000)
/lib/ld-linux.so.2 (0x00321000)
$ ldd /usr/sbin/sendmail
linux-gate.so.1 => (0x001a0000)
libssl.so.4 => /lib/libssl.so.4 (0x0036b000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0x009c8000)
libdb-4.2.so => /lib/tls/i686/libdb-4.2.so (0x008d5000)
[snip]
So... it may mean that sendmail is failing to execute because you have
a version mismatch. Have you tried updating your system lately? You
can try testing this out by running sendmail on the command line.
Something like this might make a nice test:
$ sendmail address(a)example.com
From: user(a)example.com
To: address(a)example.com
This is a test.
.
The actual addresses in the headers that you type don't really matter,
so long as you *do not* specify the -t option to sendmail.
Do you get the same messages?
--
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D
4:09 p.m.
On Sun, 6 Nov 2005, Derek Martin wrote:
> Berkeley DB version mismatch: compiled against 4.1.25, run-time
linked
> against 4.3.27
>
> What the heck does THAT mean?
Well, the only program you're executing that's linked against Berkely
DB is sendmail (called indirectly by /bin/mail):
CRAP! Derek, you figured it out for me. In FC1, I compiled my own sendmail
to get the latest version...8.14.5. So, when FC4 upgraded my machine,
it saw I had a "current" version, and happily ignored it, even though it
won't work.
Phew!
$ ldd `which grep`
So... it may mean that sendmail is failing to execute because you have
a version mismatch. Have you tried updating your system lately?
(Bangs head against wall, shattering the wall) Sigh. Yes. Wow, do I
feel dumb.
You
can try testing this out by running sendmail on the command line.
Something like this might make a nice test:
$ sendmail address(a)example.com
From: user(a)example.com
To: address(a)example.com
This is a test.
.
The actual addresses in the headers that you type don't really matter,
so long as you *do not* specify the -t option to sendmail.
Do you get the same messages?
Yep. But I "downgraded"/reinstalled and it works great. Thanks!
*******************************************************************************
Gilbert Sebenste ********
(My opinions only!) ******
Staff Meteorologist, Northern Illinois University ****
E-mail: sebenste(a)weather.admin.niu.edu ***
web: http://weather.admin.niu.edu **
Work phone: 815-753-5492 *
*******************************************************************************
6751
days inactive
6755
days old
9 comments
3 participants
participants (3)
-
Derek Martin -
Gilbert Sebenste -
James Wilkinson