Hi!

Martin> Hi, Martin> should I worry about the following?:

Martin> How-To-Repeat:

Martin> 021018 13:19:33 mysqld started Martin> crashing: /proc/613/exe: Permission denied Martin> BFD load failed.. Martin> /usr/local/mysql/libexec/mysqld: ready for connections

<cut>

Martin> # ls -la /usr/local/mysql-BK-20021018/libexec/mysqld Martin> -rwxr-xr-x 1 bioadmin mysql 3072359 Oct 18 13:00
/usr/local/mysql-BK-20021018/libexec/mysqld

Do you really mean that you get first an error message but mysqld starts as normally ?

This is not normal and could be a bug in the thread library you are using. The 'crashing:' text doesn't come from MySQL but from system library.

If you could try to compile MySQL with debugging and try to figure out what system call causes this we could try to figure out a workaround for this.

Martin> Another trial using strace gives me:

<cut> Unfortunately this doesn't tell us which library/system call that prints the error message.

Martin> BTW: Inspecting the trace log tells me, there are a lost of PATH's Martin> hardcoded into binaries, and very often it tries to open ./anything
before Martin> using $BINDIR/anything or using similar variable set by mysqld_safe. Is Martin> that expected?

Can you give us some examples of this ? Especially when searching after my.cnf files mysqld will try some pre-determinate paths, but appart from that this shouldn't happen.

Martin> I'm starting /etc/rc3.d/mysql.server as root from current Martin> working directory /usr/local. It seems, I'd better do Martin> "cd /usr/local/mysql":

The mysqld_safe script assumes that you are in the directory where mysqld is installed; This enables you to have many different versions of MySQL on the same machine (which makes it easy to upgrade and test new versions)

Martin> stat64("/usr/local/data/mysql", 0xbffff7ac) = -1 ENOENT (No such file or
directory) Martin> stat64("./share/mysql/english/errmsg.sys", 0xbffff78c) = -1 ENOENT (No
such file or directory)

The above is normal when you start mysqld_safe from the wrong place.

<cut>

Martin> But those are probably only of interrest until my.cnf is found.

Actually you should not get any errors like the above if mysqld fines a my.cnf file as my.cnf files are searched for first. After this mysqld should use the paths from the my.cnf file instead of any internal paths.

Regards, Monty