<html> <head> <style></style> </head> <body class='hmmessage'> Hi Cristian<div><br></div><div>Thanks for your less than helpful reply. had you have bothered to RTFT (last T for thread)</div><div>you would have seen that I am already aware of the fact that when invoked as sh that</div><div>bash will follow the POSIX standard and that the below was merely for demonstrating the</div><div>results so that when compared with the upstart script it shows that it still is using sh</div><div>instead of bash even though I have compiled it as such.</div><div><br></div><div>grail<br><br>> Date: Tue, 14 Jun 2011 09:30:30 +0200<br>> From: cristian.ionescu-idbohrn@axis.com<br>> To: upstart-devel@lists.ubuntu.com<br>> Subject: Re: Process substitution into loop<br>> <br>> On Tue, 14 Jun 2011, Grail Dane wrote:<br>> ><br>> > Under bash I get:<br>> > ip link set dev lo upip link set dev eth0 upip link set dev sit0 up<br>> ><br>> > Under sh I get:<br>> > line 6: syntax error near unexpected token<br>> > `<'line 6: `done< <(ip link | awk '/^[0-9]/ && gsub(/:/,""){print $2}')'<br>> <br>> RTFM, `man bash'?<br>> <br>> If bash is invoked with the name sh, it tries to mimic the<br>> startup behavior of historical versions of sh as closely as<br>> possible, while conforming to the POSIX standard as well.<br>> <br>> > Once compiled and installed is there any way to check what shell it<br>> > thinks is the default?<br>> <br>> Maybe:<br>> <br>> $ readlink /bin/sh<br>> <br>> could help?<br>> <br>> <br>> Cheers,<br>> <br>> -- <br>> Cristian<br>> <br>> -- <br>> upstart-devel mailing list<br>> upstart-devel@lists.ubuntu.com<br>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel<br></div> </body> </html>