tlack,
Saturday, June 08, 2002, 2:19:39 AM, you wrote:
>Description:
t> Change datadir in /etc/my.cnf or elsewhere. Start server (i.e.,
t> /usr/local/share/mysql/mysql.server start) and then try to stop it
t> (/usr/local/share/mysql/mysql.server stop)
All worked fine for me.
>How-To-Repeat:
t
All init.d daemons take one of two options. These are "start" and "stop".
Init supplies the correct option when changiing run levels.
Where the daemon resides varies among versions of UNIX/Linux.
[EMAIL PROTECTED] wrote:
>>Description:
>>
>regarding mysql.server daemon
>
>>How-To-Repeat:
>>
>
TED]>
> To: "Sinisa Milivojevic" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; "mysql" <[EMAIL PROTECTED]>
> Sent: Monday, July 23, 2001 5:07 PM
> Subject: Re: [mysql.server stop fails under OpenBSD 2.9]
>
>
>> I tried it, and mysql
: +49-30-46307-388
- Original Message -
From: "Walter Lee Davis" <[EMAIL PROTECTED]>
To: "Sinisa Milivojevic" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "mysql" <[EMAIL PROTECTED]>
Sent: Monday, July 23, 2001 5:07 PM
Subject: Re: [mys
I tried it, and mysqladmin just sits there and never returns the prompt.
Looking at it from another ssh session, I see that mysqladmin and
safe_mysqld and mysql are all still active. Perhaps admin is killing and
safe is restarting just as fast. Mysqladmin did not respond to Control-C,
nor did it l
Walter Lee Davis writes:
> Could this be related to the problems which cause mysql to be almost
> un-killable on MacOS X? I have tried to use mysqladmin to stop the server,
> but the only thing that will do it is 'kill -9', and if I had started it
> with safe_mysqld, then it comes bouncing right b
Could this be related to the problems which cause mysql to be almost
un-killable on MacOS X? I have tried to use mysqladmin to stop the server,
but the only thing that will do it is 'kill -9', and if I had started it
with safe_mysqld, then it comes bouncing right back. I can't even find
safe_mysql
[EMAIL PROTECTED] writes:
> >Description:
> mysql.server stop fails to stop the server even though
> mysql.server start was used to start it.
>
> The INSTALL-SOURCE text file recommends using the script
> support-files/mysql.server to start mySQL at boot-time.
>
As far as my fuzzy memory of the install process goes, the install_db
script made the /etc/mysql directory and put the my.cnf file there. In the
my.cnf file, it says
# You can copy this to one of:
# /etc/mysql/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (
Joel Gwynn writes:
> I'm running mysql 3.23.33 on debian. I'm using /etc/init.d/mysql.server
> to start up and shut down mysql server. My configuration file is
> /etc/mysql/my.cnf. In that file, I've set my socket as follows:
>
> socket = /var/run/mysqld/mysqld.sock
>
> When
Joel:
I'll take another shot. Do you have spaces in your command? Remove
them.
Change : socket = /var/run/mysqld/mysqld.sock
To: socket=/var/run/mysqld/mysqld.sock
Cheers,
Kent
-
Before posting, please chec
While that is definitely the kind of pinheaded mistake that I'm used to
making, that's not what's happening. I just looked at the file again and
mysql.server is also ignoring things like the pid file and the log file :(
thanks anyway
At 12:51 PM 2/26/01 -0800, you wrote:
>
>make sure that you s
make sure that you set the sock parameter in both the [client] and [mysqld]
sections of the configuration file. This is one of my favorite errors :-/
Best,
Kyle
On Monday 26 February 2001 12:04, Joel Gwynn wrote:
> I tried /etc/my.cnf and got the same results. As far as $DATADIR or $HOME
> a
I tried /etc/my.cnf and got the same results. As far as $DATADIR or $HOME
are concerned, I don't see them when I do 'printenv'. Is there another way
to find out if those may be set, and by what?
thanks.
At 02:33 PM 2/26/01 -0500, Kent Hoover wrote:
>Sorry. Sent the last message before I was do
If you are installing from a binary release that you created, and need
to fix
save_mysqld after each installation, then you should complain to the
person that
created the binary release.
Or did I miss something?
Quentin Bennett wrote:
>
> Hi,
>
> Each time I install mysql from a binary releas
On Thu, Feb 01, 2001 at 02:12:03PM +1300, Quentin Bennett wrote:
> Hi,
>
> Each time I install mysql from a binary release that I have created,
> I have to modify safe_mysqld so that it can be called from
> mysql.server.
>
> This is because safe_mysqld checks to see if it knows what is going
> o
16 matches
Mail list logo
