[Bug 689563] Re: Mawk and mysql conflict

[Caleb Maclennan]

Thanks for your suggestions Elan. I tried them over here but
unfortunately I still get the same original error. I've played with it a
dozen ways now and what awk is doing with this code defies my
imagination. Going back to Artur's code works, but any change to that
and it throws up. Simply doing something as simple as substituting $1
for a copy of the variable make it die. Not explicitly matching for the
end of string makes it die. Taking too big a bite of chocolate while
debugging makes it die.

Frankly after failing to make awk behave the whole stupid eval/awk gig
inside this init script is starting to look like a crazy hack. Thoughts?

-- 
You received this bug notification because you are subscribed to PLD
Linux.
https://bugs.launchpad.net/bugs/689563

Title:
  Mawk and mysql conflict

Status in PLD Linux Distribution:
  Fix Released

Bug description:
  [root at pld-laptop ~]# service mysql restart
Error: datadir specified in /var/lib/mysql/mysqld.conf should be
/var/lib/mysql/mysqldb/db MySQL can't be run.

[root at pld-laptop ~]# grep -v "^#" /etc/mysql/clusters.conf

mysqld.conf=/var/lib/mysql


[root at pld-laptop ~]# rpm -qv mysql
mysql-5.1.52-1.i686

[root at pld-laptop ~]# rpm -qv mawk
mawk-1.3.4-0.20100625.1.i686


mawk build on carme, but some time ago there were in th-foo (I don't
know, in which th-*), and --upgrade-dist didn't "downgrade" mawk.