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