Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Aug 2002 16:50:51 +1000
From:      Tim Robbins <tjr@FreeBSD.ORG>
To:        Miha Nedok <mike@mike.unix-systems.net>
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: sh(1) problems after upgrade
Message-ID:  <20020828165051.A32666@dilbert.robbins.dropbear.id.au>
In-Reply-To: <20020827215400.L60568-100000@defiant.zrcalo.si>; from mike@mike.unix-systems.net on Tue, Aug 27, 2002 at 09:54:16PM %2B0200
References:  <20020827215400.L60568-100000@defiant.zrcalo.si>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 27, 2002 at 09:54:16PM +0200, Miha Nedok wrote:

> sh(1) changes affect it's behaviour.
> The rc script for MySQL coming with the port doesn't work.
> 
> /usr/local/etc/rc.d/mysql-server.sh start
> /usr/local/etc/rc.d/mysql-server.sh: 6: Syntax error: "&&" unexpected

I believe this has been fixed by revision 1.3 of databases/mysql323-server/
files/mysql-server.sh. It's unfortunate that it completely breaks some
incorrect scripts, but a command like:

	foo & && echo 'foo has been started'

never worked properly, and was interpreted by the shell as:

	foo & true && echo 'foo has been started'
	      ^^^^

This will be pointed out in the release notes for 4.7 because so many
people have asked me about it.


Tim

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020828165051.A32666>