SOLUTION: Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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/interfaces files. It turns out that one does NOT need to add the pre-up line, the script gets run by run-parts automatically..presumably if it's executable which it was yes the manpage mentions run-parts but it does not explicitly say one does not need to mention the pre-up line for scripts that are the special directories.i think a little clarification may be in order for the manpage. NOTE one can run any command in the pre-up line. It's a simple matter to put in pre-up env somefile to see what environment variables are set. IN particular PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin and consequently one could run iptables directly No doubt the more learned users on the list are wondering what all the fuss is all about ;-) -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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 complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ 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 running sarge btw, with 2.4.23 kernel version. Thanks . Siggy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
Am Freitag, 23. Januar 2004 18:49 schrieb Walter Tautz: 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 complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ 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 running sarge btw, with 2.4.23 kernel version. Just a guess: # cat myfilter | recode ibmpc..lat1 myfilter.new Try if myfilter.new executes. I had this problem after transferring one file via ftp some time ago. If its not the problem, well - it was just a guess ;-) Cajus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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 It's not something trivial like a DOS linefeed on the end, making the system look for /bin/sh^M is it? Steve -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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 It's not something trivial like a DOS linefeed on the end, making the system look for /bin/sh^M is it? Steve -- Nope. It was created directly on the box with vi... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
In article [EMAIL PROTECTED] you wrote: which DOES work. I wonder why it's complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. you may want to show us the exact output of that complain. Gruss Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
Am 2004-01-21 14:11:39, schrieb Walter Tautz: specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter: which DOES work. I wonder why it's complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. NOTE if I take it out it completely fails... Hello, I have the same Error if the file is not executable ! chmod 700 /etc/network/if-pre-up.d/myfilter Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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 complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ 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 running sarge btw, with 2.4.23 kernel version. Thanks . Siggy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
Am Freitag, 23. Januar 2004 18:49 schrieb Walter Tautz: 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 complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ 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 running sarge btw, with 2.4.23 kernel version. Just a guess: # cat myfilter | recode ibmpc..lat1 myfilter.new Try if myfilter.new executes. I had this problem after transferring one file via ftp some time ago. If its not the problem, well - it was just a guess ;-) Cajus
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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 It's not something trivial like a DOS linefeed on the end, making the system look for /bin/sh^M is it? Steve --
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
In article [EMAIL PROTECTED] you wrote: which DOES work. I wonder why it's complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. you may want to show us the exact output of that complain. Gruss Bernd
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
Am 2004-01-21 14:11:39, schrieb Walter Tautz: specically I have a /bin/sh script in /etc/network/if-pre-up.d/myfilter: which DOES work. I wonder why it's complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. NOTE if I take it out it completely fails... Hello, I have the same Error if the file is not executable ! chmod 700 /etc/network/if-pre-up.d/myfilter Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
On Wed, Jan 21, 2004 at 02:11:39PM -0500, Walter Tautz wrote: #! /bin/sh [...] which DOES work. I wonder why it's complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. Hi, ever tried the line #!/bin/sh ? all my scripts seem to lack the space. hope I'm right :-) Horst. -- Join the army, see the world, meet interesting, exciting people, and kill them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
On Wed, Jan 21, 2004 at 02:11:39PM -0500, Walter Tautz wrote: #! /bin/sh [...] which DOES work. I wonder why it's complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. Hi, ever tried the line #!/bin/sh ? all my scripts seem to lack the space. hope I'm right :-) Horst. -- Join the army, see the world, meet interesting, exciting people, and kill them.
Re: get error: /bin/sh: line1: myfilter: command in boot messages...
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 complaining about the line #! /bin/sh during the boot messages. Note no such output is in dmesg. The shebang bites again :) Here's some reading on it: http://www.in-ulm.de/~mascheck/various/shebang/ Thanks . Siggy
