6 messages in com.mysql.lists.mysqlRe: no show
FromSent OnAttachments
da...@straylight.org05 Dec 2000 20:51 
Sinisa Milivojevic06 Dec 2000 04:25 
David Andrew Michael Noelle06 Dec 2000 12:15 
Sinisa Milivojevic07 Dec 2000 04:46 
David Andrew Michael Noelle07 Dec 2000 07:16 
Sinisa Milivojevic07 Dec 2000 09:30 
Subject:Re: no show
From:David Andrew Michael Noelle (da@straylight.org)
Date:12/07/2000 07:16:24 AM
List:com.mysql.lists.mysql

David Andrew Michael Noelle writes:

None of my config or startup files have any mention of "--skip-show-databases". I didn't even know there was such an option.

Is there somewhere I should look other than /etc/my.cnf, /usr/local/etc/my.cnf and /etc/rc.d/rc.mysql if mysqld is being started by root. According to find -exec grep, the phrase "skip-show-databases" does not appear anywhere in /etc.

The permissions look right to me. What permissions on what files could cause "show" to fail while "select" works normally?

mysqld was indeed running as root, although I specified user=data when I configured it and set user=data in the startup script that was running it. I prefer to have one user for all of my database daemons as opposed to user msql for mSQL and user mysql for MySQL and user pgsql for PostgreSQL.

I manually restarted it with safe_mysqld --user=data and encountered even more problems, because "data" didn't own /usr/local/var. I changed the data directory to /usr/local/var/mysql, and chown'ed that to "data", because /usr/local/var is used by other programs, including Gnome.

Now mysqld is running as "data" and using /usr/local/var/mysql as its data directory. /usr/local/var/mysql and all of its subdirectories, and all of their contents are owned by "data". /usr/local/var/mysql is mode 755, subdirs are mode 700, and their contents are mode 600. After all these changes, I'm still having the same problem. If those are not the correct permissions, what are?

From: Sinisa Milivojevic <sin@mysql.com> Date: Thu, 7 Dec 2000 14:46:36 +0200 (EET)

Check the ownership and umask of all files and subdirs under datadir, if mysqld is not run under root uid.

I did. See the last paragraph above: - mysqld is running as "data" - datadir is owned by "data", mode 755 - all subdirs are owned by "data". mode 700 - all files in all subdirs are owned by "data", mode 600

You still haven't told me what the permissions, or "umask", _should_ be, nor what possible ownership or permissions (given that when this problem arose, mysqld was running as root) could possibly have caused this kind of failure.

If that is Ok, then the other possbile cause of problems might be in your system C libs.

As it seems you are using Linux, what glibc and kernel versions do you have ??

Linux 2.2.16 glibc 2.2