Hi -

On line 117 of mysqld_safe in the 4.0.16 source distribution, the
socket name (/tmp/mysql.sock) is hard coded. I noticed this when I
installed 4.0.16 alongside an older version and then started 4.0.16.
Although I had set the socket to a different location in $MYSQL_HOME/var,
4.0.16 obligingly deleted the older version's socket.



Garey Mills
Library Systems Office
UC Berkeley



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org

Garey Mills writes:
>
> Hi -
>
> On line 117 of mysqld_safe in the 4.0.16 source distribution, the
> socket name (/tmp/mysql.sock) is hard coded. I noticed this when I
> installed 4.0.16 alongside an older version and then started 4.0.16.
> Although I had set the socket to a different location in $MYSQL_HOME/var,
> 4.0.16 obligingly deleted the older version's socket.
>
>
>
> Garey Mills
> Library Systems Office
> UC Berkeley
>

Hi!

Thank you for your message.

Actually, that is the last option for the socket location.

If neither --socket option is supplied to mysqld_safe, nor is
MYSQL_UNIX_PORT defined as environmental variable, then some path has
to be specified.

--

Sincerely,

--
For technical support contracts, go to https://order.mysql.com/?ref=msmi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sinisa [at] mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB
/_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinator
<___/ www.mysql.com Larnaca, Cyprus


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org

Okay, but my.cnf defines a new socket and mysqld_safe does not pick it up.
Does mysqld_safe need an explicit argument apart from what's found in
my.cnf?

Garey Mills
Library Systems Office
UC Berkeley


On Wed, 3 Dec 2003, Sinisa Milivojevic wrote:

> Garey Mills writes:
> >
> > Hi -
> >
> > On line 117 of mysqld_safe in the 4.0.16 source distribution, the
> > socket name (/tmp/mysql.sock) is hard coded. I noticed this when I
> > installed 4.0.16 alongside an older version and then started 4.0.16.
> > Although I had set the socket to a different location in $MYSQL_HOME/var,
> > 4.0.16 obligingly deleted the older version's socket.
> >
> >
> >
> > Garey Mills
> > Library Systems Office
> > UC Berkeley
> >
>
> Hi!
>
> Thank you for your message.
>
> Actually, that is the last option for the socket location.
>
> If neither --socket option is supplied to mysqld_safe, nor is
> MYSQL_UNIX_PORT defined as environmental variable, then some path has
> to be specified.
>
> --
>
> Sincerely,
>
> --
> For technical support contracts, go to https://order.mysql.com/?ref=msmi
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sinisa [at] mysql.com>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB
> /_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinator
> <___/ www.mysql.com Larnaca, Cyprus
>
>


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org

Garey Mills writes:
> Okay, but my.cnf defines a new socket and mysqld_safe does not pick it up.
> Does mysqld_safe need an explicit argument apart from what's found in
> my.cnf?
>
> Garey Mills
> Library Systems Office
> UC Berkeley
>

mysqld_safe reads options under [mysqld_safe] options header.

If you have put that option there, and not under [mysqld] then what
you are reporting is a bug.

--

Sincerely,

--
For technical support contracts, go to https://order.mysql.com/?ref=msmi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <sinisa [at] mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB
/_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinator
<___/ www.mysql.com Larnaca, Cyprus


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org