----- Original Message -----
From: "Rusty"
To: "SuSE"
Sent: 12 February 2000, Saturday 03:35
Subject: [SLE] Mysql
| I recently bought the book "MySQL" by Paul DuBois. I planned to
| do everything by the book this time. Honest; No cheating. I am
| determined to finally exercize the discipline necessary to learn a
| program the way you're supposed to, not wing it.
If you want a good mysql book, consider the book _MySQL & mSQL_ published by
O'Reilly (ISBN 1-56592-434-7). Although it's not platform-specific (and
certainly not Linux-distro specific), it covers all the ins and out of the
software and associated APIs.
| Alas, and alack! First I read the README and then the README.SuSE
| and I find that Suse has made a decision to locate the files
| somewhere other than the traditional place until everyone gets
| their act together and settles on a standard place for the program
| to be installed. I'll go along with that.
mysql can live anywhere; like any program, it lives where you tell it to
live. SuSE puts it in one place, Debian puts it in another; as long as it
runs and you know where it is, it shouldn't be an issue. In any case, you
can change where the mysql daemon looks for its data/config files at runtime
using cool options like --basedir.
PS -- The mysql daemon doesn't need root privs to run. It uses a high
unprivledged port (3306) and doesn't require any accessible-only-by-root
files or dirs. SuSE (at least 6.2) runs the daemon as root which is lame.
There is an option, --user, to run the mysql daemon as any given user. Of
course you need to ensure that tables, etc, can be read and written by
whatever user you choose to run the daemon as.
| I set up and get the Apache server running and then I turn to the
| book.
|
| It says to start the mysql sever by typing mysql options, which I
| do.
No. You need to start the daemon via mysqld. If you are using the SuSE
mysql package, you can start the daemon with ``rcmysql start'' (if the user
you want to run the daemon can run the rc script). Or you can use the
script ``safe_mysqld'' that comes with the mysql package. You will probably
have to edit this script if you want to use the --user option stated above.
| The response I receive is ERROR 2002: Can't connect to local MySQL
| server through socket '/tmp/mysql.sock' (111)
Server's not running. :)
| My question; Is the reason I'm having trouble because of the
| non-standard installation suse has decided to temporarily use or
| is it the standard Unix/Linux you can't get there from here
| because the documentation is out dated when it's published because
| the developers have changed the distribution?
No and no.
| BTH, does anybody know where the ERROR code list is located?
Unfortunately, no.
| Any help is appreciated.
|
| Rusty
Hope this helps,
KW
/*
** Keith Warno
** Make Us An Offer, Inc.
** Real-Time Online Haggling
** http://www.HaggleWare.com/
*/
--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/