Greg Willits wrote:
On May 20, 2004, at 11:08 AM, Sasha Pachev wrote:
Greg Willits wrote:
I have two mysql apps running on the same machine (OS X 10.3.3). A
mysql 3.23.54 on port 14551, and a mysql 4.0.16 on 3306. Each has a
config file specifying the port and a unique socket name in /tmp.
They
Greg Willits wrote:
On May 20, 2004, at 11:08 AM, Sasha Pachev wrote:
Greg Willits wrote:
I have two mysql apps running on the same machine (OS X 10.3.3). A
mysql 3.23.54 on port 14551, and a mysql 4.0.16 on 3306. Each has a
config file specifying the port and a unique socket name in /tmp.
They
Greg Willits wrote:
Greg Willits wrote:
On May 20, 2004, at 11:08 AM, Sasha Pachev wrote:
Greg Willits wrote:
I have two mysql apps running on the same machine (OS X 10.3.3). A
mysql 3.23.54 on port 14551, and a mysql 4.0.16 on 3306. Each has a
config file specifying the port and a unique socket
Greg Willits wrote:
I have two mysql apps running on the same machine (OS X 10.3.3). A mysql
3.23.54 on port 14551, and a mysql 4.0.16 on 3306. Each has a config
file specifying the port and a unique socket name in /tmp. They have
coexisted just peachy for a very long time.
Now however, w/o
On May 20, 2004, at 11:08 AM, Sasha Pachev wrote:
Greg Willits wrote:
I have two mysql apps running on the same machine (OS X 10.3.3). A
mysql 3.23.54 on port 14551, and a mysql 4.0.16 on 3306. Each has a
config file specifying the port and a unique socket name in /tmp.
They have coexisted just
I have two mysql apps running on the same machine (OS X 10.3.3). A
mysql 3.23.54 on port 14551, and a mysql 4.0.16 on 3306. Each has a
config file specifying the port and a unique socket name in /tmp. They
have coexisted just peachy for a very long time.
Now however, w/o any changes to either
