MySQL Forums
Forum List  »  Perl

Re: Problem Connecting to Server with Perl
Posted by: Eric Robertson
Date: September 09, 2010 06:34AM

Well I've tried again to locate my.ini without success. However there are a couple of my.cnf files that have a [mysqld] section. One is at /Applications/MAMP/tmp/mysql and the other at /Applications/MAMP PRO 1.7.1/MAMP They both seem to be identical, with most of the section being commented out, apart from one part. The effective parts in the second of these, which is presumably the one that is in force as I am using the PRO version of MAMP, is a follows:

#port = 9999
socket = /Applications/MAMP/tmp/mysql/mysql.sock
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!

# Replication Master Server (default)
# binary logging is required for replication

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

The other version of my.cnf, in the tmp folder, is identical except that the "MAMP_skip-networking_MAMP" line is replaced by the commented out line "#skip-networking".

Just one other thing. My MAMP PRO front end I see gives me access to the my.cnf template so that it can be amended, and this is identical to the MAMP PRO one set out above, which seems to confirm that this is the effective version.

Does this give you any clue as to the use of pipes?

Options: ReplyQuote

Written By
Re: Problem Connecting to Server with Perl
September 09, 2010 06:34AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.