Murat Bicer wrote:
killall freevrrpd > /dev/null 2>&1 & && echo -n 'freevrrpd'
The construction 'a & && b' has always been
complete nonsense and the shell no longer accepts it.
(The '&&' means "check the output of the
preceding command", which isn't possible
with 'a &' being run in the backg
Sorry about the question.
It was in the release notes.
sh(1) no longer accepts invalid constructs as command & && command, &&
command, or || command.
On Fri, 24 Jan 2003 10:43:22 -0500, "Murat Bicer" <[EMAIL PROTECTED]> said:
> Has something changed in sh between these versions:
>
> I get a we
Has something changed in sh between these versions:
I get a weird error on some of my scripts
#!/bin/sh
case "$1" in
start)
[ -x /usr/local/sbin/freevrrpd ] &&
/usr/local/sbin/freevrrpd &&
echo -n ' freevrrpd'
;;
stop)
