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 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)
> killall freevrrpd > /dev/null 2>&1 & && echo -n '
> freevrrpd'
> ;;
> *)
> echo ""
> echo "Usage: `basename $0` { start | stop }"
> echo ""
> exit 64
> ;;
> esac
> ha1# sh -x /home/murat/freevrrpd.sh stop
> /home/murat/freevrrpd.sh: 8: Syntax error: "&&" unexpected
>
>
> Murat Bicer
> [EMAIL PROTECTED]
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
>
Murat Bicer
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
