>
> Hello,
>
> I have the same Error if the file is not executable !
>
> chmod 700 /etc/network/if-pre-up.d/myfilter
>
> Greetings
> Michelle
>
recall that I had a script called myfilter (/bin/sh script)
in /etc/network/if-pre-up.d/ AND I had the line
pre-up myfilter in my /etc/network/interfac
>
> Hello,
>
> I have the same Error if the file is not executable !
>
> chmod 700 /etc/network/if-pre-up.d/myfilter
>
> Greetings
> Michelle
>
recall that I had a script called myfilter (/bin/sh script)
in /etc/network/if-pre-up.d/ AND I had the line
pre-up myfilter in my /etc/network/interfac
On Fri, 23 Jan 2004, Steve Kemp wrote:
> On Fri, Jan 23, 2004 at 12:49:11PM -0500, Walter Tautz wrote:
>
> > Doesn't seem to make a difference whether there is a space after #! or not.
> > still get the same annoying message. I suppose it doesn't matter
>
On Fri, 23 Jan 2004, Steve Kemp wrote:
> On Fri, Jan 23, 2004 at 12:49:11PM -0500, Walter Tautz wrote:
>
> > Doesn't seem to make a difference whether there is a space after #! or not.
> > still get the same annoying message. I suppose it doesn't matter
>
On Thu, 22 Jan 2004, Bernd S. Brentrup wrote:
> On Wed, Jan 21, 2004 at 02:11:39PM -0500, Walter Tautz wrote:
> > specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter:
> >
> > #! /bin/sh
> [...]
> > which DOES work. I wonder why it's co
On Thu, 22 Jan 2004, Bernd S. Brentrup wrote:
> On Wed, Jan 21, 2004 at 02:11:39PM -0500, Walter Tautz wrote:
> > specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter:
> >
> > #! /bin/sh
> [...]
> > which DOES work. I wonder why it's co
specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter:
#! /bin/sh
iptables -X
iptables -F
iptables -A OUTPUT -p tcp --destination-port telnet -j REJECT
which DOES work. I wonder why it's complaining about the line #! /bin/sh
during the boot messages. Note no such output is
specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter:
#! /bin/sh
iptables -X
iptables -F
iptables -A OUTPUT -p tcp --destination-port telnet -j REJECT
which DOES work. I wonder why it's complaining about the line #! /bin/sh
during the boot messages. Note no such output is
just wondering if this would be a good idea. We currently have
>80 machines that do an update once a day on this host so
I think it may be a good idea to mirror the archive locally, say
once a day via rsync?
walter
just wondering if this would be a good idea. We currently have
>80 machines that do an update once a day on this host so
I think it may be a good idea to mirror the archive locally, say
once a day via rsync?
walter
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". T
10 matches
Mail list logo
