Re: ip-up local

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Only thing I can mention is make sure that you chmod +x /etc/ppp/ip-up.local

I also occasionally put in echo's and create my own log file in /tmp. 
logger is also an excellent solution to put entries into
/var/log/messages.

   - kevin

On Fri, 06 Aug 2004 00:43:40 +0200, Alexander Dalloz
<alexander.dalloz@xxxxxxxxxxxxxxxx> wrote:
> Am Fr, den 06.08.2004 schrieb edwarner99@xxxxxxxxx um 0:18:
> 
> > How can I tell if the script in /etc/ppp/ip-up.local
> > is being executed, or where the problem lies?
> 
> > I have the following in /etc/ppp/ip-up.local:
> >
> > #!/bin/bash
> > PATH=$PATH:/sbin:/usr/sbin:/bin:/usr/bin
> > export PATH
> >
> > sh /etc/firestarter/firewall.sh
> 
> Add to the end of the script following line:
> 
> /usr/bin/logger -t `basename $0` -p daemon.notice "ip-up.local executed"
> 
> and observe the messages log file during connects. I don't see why it
> shouldn't be executed. Though /etc is no good place for executive
> scripts. If you want to use $1 and $6 in the firewall.sh script you
> should know that these variables are not available there, like you did
> set things up.
> 
> Alexander
> 
> --
> Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
> Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.7-1.494.2.2smp
> Serendipity 00:40:30 up 1 day, 18:08, load average: 0.23, 0.24, 0.15
> 
> 
>



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux