I have a project I'm working on for a family member: Their Redhat box
has a crontab to dial their ISP at a given time and hangs up a given
time. Should be simple right?
Well my crontab command works to establish the connection but I think
it's failing at taking the connection down for some reason.
here's the crontab stuff
#run at 8AM
0 8 * * * /sbin/ifup ppp0
0 12 * * * /sbin/ifdown ppp0
Like I say "up" is no problem. Down is the question. Here is
PERSIST=yes <<<< is this keeping the line from going down, or just
keeping it up while it's supposed to be up
Does anybody see what is going on? I am a little hamstrung in my
debugging attempts as the box is remote, and there's no one there who
can help me. There aren't any relevant messages in syslog nor and the
mail to root doesn't show anything germane. It just fails to hangup.
Does the "persist" option in /etc/sysconfig/network-scripts/ifcfg-ppp0
ALso, in the course of trying to set this up, it seems from the scripts
and observation that if anyone even a user established the
connection--like with the usernet program--the /sbin/ifdown ppp0 command
will fail. Can this be correct? If so isn't there a way around it? I'm
pretty amazed that Redhat or whoever wrote these scripts would design
them in such a way that root or process owned by root would not have the
authority to shut off the network connection at will. Here is what I'm
talking about in ifdown-ppp
if [ ! -f $file ]; then
# ppp isn't running, or we didn't start it <<<<what is up with
So if user starts ppp0 up root's scheduled job to tear down the
connection will fail?
Please help me figure out how to set this crontab to take precedence
over RH's network scripts. I just want up orderly _on and off_ periods
for the network and I can't believe it's this difficult.
Thanks for Your Help,