On Wed, Jan 22, 2014 at 05:45:39PM +0100, Arturo Borrero Gonzalez wrote: > On 14 January 2014 16:16, Patrick McHardy <kaber@xxxxxxxxx> wrote: > > On Tue, Jan 14, 2014 at 03:00:14PM +0000, Sam Liddicott wrote: > >> I realise a solution is reached, but an alternative in common use is > >> mentioned here for completeness; > >> > >> #! /usr/bin/env nft -f > >> > >> it is commonly used to invoke interpreters whose path is unknown but > >> which can be expected to be on the PATH > > > > I'm find either way. Unless there are arguments for not using env, > > this seems like the simpler fix. > > > Using env with an additional argument (the '-f') seems to fail in my system. > > ===8<=== > #!/usr/bin/env nft -f > list table filter > ===8<=== > > % ./test > /usr/bin/env: nft -f: No such file or directory I guess lets just keep it this way. Thanks. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
