Hello!
Given the latest security advisory about 'resolv', I decided to upgrade
my FreeBSD 4.6.1-RELEASE-p10 server to 4.7-RELEASE-p1 via the usual
cvsup and buildworld magic.
Everything else seems to have gone fine, but to my surprise after
upgrading two of the ports using scripts in /usr/local/etc/rc.d to
start didn't. One of them is MySQL server. It is started via
/usr/local/etc/rc.d/mysql-server.sh script, which looks like this:
-----------------------------------------------------------------------
#!/bin/sh
case "$1" in
start)
if [ -x /usr/local/bin/safe_mysqld ]; then
# THE BELOW IS ACTUALLY ALL ON ONE LINE
/usr/local/bin/safe_mysqld --user=mysql > /dev/null & && echo -n
'mysqld'
# THE ABOVE IS ACTUALLY ALL ON ONE LINE
fi
;;
<rest of the script snipped as irrelevant>
-----------------------------------------------------------------------
I determined from ps output that mysqld is not running. Then I tried to
run '/usr/local/etc/rc.d/mysql-server.sh start' from the command line,
and got the error message 'Syntax error, unexpected "&&"' (I write
this from memory, so the message is not exact but the meaning is).
This mysql-server.sh script has been there since the server was
originally installed and it has never been touched. The server has been
upgraded from 4.3 to 4.5 to 4.6, and now this.
For now I just broke the one line which caused the problem into two:
/usr/local/bin/safe_mysqld --user=mysql > /dev/null &
echo -n 'mysqld'
but this just isn't right.
The other script which doesn't start is pwcheck.sh (I think this is
installed as part of Cyrus SASL or IMAPD, not sure exactly what it is
used for <g>). The start line there also contains the '& &&' sequence:
${sasl_pwcheck_program} & && echo -n " pwcheck"
How should I really correct the problem (the shotgun approach would
probably be to upgrade the relevant ports to latest, but I'm looking
for something lighter).
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* Jesus has changed your life. Save changes (Y/N)?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
