----- Original Message ----- From: "Juan Pedro Reyes Molina" <[EMAIL PROTECTED]>
To: "Hassan Schroeder" <[EMAIL PROTECTED]>
Cc: "mysql general list" <mysql@lists.mysql.com>
Sent: Saturday, June 25, 2005 2:08 PM
Subject: Re: starting mysql 4.1.12 on Ubuntu Linux


hello, Hassan

which mysql gives me /usr/bin/mysql. echo $PATH shows me that /usr/bin is the fourth try. I thougth this was windows like, where PATH is only used if program is not found in active directory.

If you wish it, currrent directory (.) should be added to $PATH.
export PATH=.:$PATH


So, I have a script in /etc/init.d called mysql and an executable in /usr/bin also called mysql that takes precedence.

/etc/init.d probably isn't (and maybe shouldn't be) in your PATH.
Less confusion if you rename /etc/init.d/mysql to mysqld.


I thought that when linux starts all scripts in /etc/init.d where given the start signal. If so I don't understand why mysql remains stopped on linux start up but wake up smoothly when I issue a manual /etc/init.d/mysql start. It looks like a bug in Ubuntu distro.

On my Solaris box, there is a directory named /etc/rc2.d. In that directory
is a symbolic link to /etc/init.d/mysqld named S99mysqld. This means that
the mysql server will be started in init state 2. In /etc/rc1.d is a symbolic
link to /etc/init.d/mysqld named K99mysqld. This means that the mysql
server will be killed in init state 1. Your /etc/rc directory structure may vary
somewhat.
ln -s /etc/init.d/mysqld /etc/rc2.d/S99mysqld


I have tried cp /etc/init.d/mysql /etc/init.d/mysqltmp but issuing /etc/init.d/mysqltmp gives me "bash: mysqltmp: command not found"

mysqltmp may not be executable.
chmod u+x mysqltmp



Hassan Schroeder wrote:

Juan Pedro Reyes Molina wrote:

With my sql stopped I go to console as root and write:

cd /etc/init.d
mysql start


At this point, try (as root)
 which mysql

It will certainly not be /etc/init.d/mysql, but somewhere in your
defined PATH; try
 echo $PATH
to see what that is

I would like to learn what's the difference between "mysql start" and "/etc/init.d/mysql start" if I'm sitting on "/etc/init.d"


'/etc/init.d/mysql' defines the executable you want to run explicitly;
'mysql' is the first instance of an executable with that name in your
PATH.

I think this error is preventing mysql from automatically starting on start up.


Probably not; look in your error logs for more information on that.

And in any case 'mysql' is generally the *client* program; *mysqld*
is the server that you want to start. Sounds like your distro has a
confusingly named startup file in /etc/init.d.

HTH!


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to