>If you have httpd running on that machine you wouldn't need to mail it
>at all.
Well, almost <g>. The purpose of the whole thing is to keep me apprised of
the client's IP address. If it changes and I don't know what it is, it's
kind of hard to get to the web site (there's no official DNS entry for the
machine). The functions of the emails are to 1) let me know if the IP
address has changed, and 2) if/when the email stops coming, let me know
there's a problem with their connection.
Thus far, I've been able to let the client know on a few occassions that
there was a problem before they knew about it, and have them reset things
appropriately to get it all going again before they needed it.
My latest endeavor has been to make it more convenient for me (via
manipulating the Subject line), and to learn more about scripting in the
Linux world. I've picked up a good chunk in the last couple of days, on my
own and with your help. For that, once again, thanks!
bd
===========================
Brad Doster
Insight Network Solutions
www.InsightNetSolutions.net
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Harry Putnam
Sent: Saturday, December 09, 2000 3:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Auto-mail Script Woes
"Brad Doster" <[EMAIL PROTECTED]> writes:
> I have a client running RH 6.2 as a DSL router. The DSL address is
dynamic,
> so to keep tabs on the system, I have a cron script that sends me its
> ifconfig once per hour. I'm trying to get mail or elm to use a subject
line
> like...
>
> 001209_1315-200.200.200.200
>
> ...where 001209 is the date sent, 1315 is time sent and 200.200.200.200 is
> the current IP address of the system. The goal is to be able to sort by
> subject so that I can easily check that the messages were sent when they
> were intended to be.
Another approach might be a system I used for a while to post my
address, time and a message on a remote webpage so my son could just
hit the URL to see my machines current address or other information
when he needed to ssh to my machine from across the state.
If you have httpd running on that machine you wouldn't need to mail it
at all. You could use a script to generate a web page hourly with the
new information appended to the list so you could readily see what was
happening. Probably wouldn't want a webserver on a router though.
Current wisdom is to use perl for stuff like that, but I don't know
much perl so I use the older sed and awk tools. The above project
would be duck soup for them.
Not a real difficult project but a good learning tool.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
