At 0:09 Uhr -0400 15.8.2001, Hans Zaunere wrote:
>Well I uncovered an interesting thing. If I use the regular old
>bin/mysql client to connect to the database (both on the same machine)
>and I run: ./mysql -uroot -p -h localhost
>Then run netstat -an , it shows that another /tmp/mysql.sock in
> > And I was thinking, since a socket is a socket (just a file descriptor)
> NO - a socket is not a file descriptor,
> something like a communication end/handshake point
> read more
> http://orkinos.cmpe.boun.edu.tr/netlab/courses/cmpe476/netprog/SocketsFAQ.txt
>
Sure they are file descriptors,
> > > > my $dbh = connect("DBI:mysql:database:localhost", "user",
> "password");
Well I uncovered an interesting thing. If I use the regular old
bin/mysql client to connect to the database (both on the same machine)
and I run: ./mysql -uroot -p -h localhost
Then run netstat -an , it sho
At 16:41 Uhr -0400 14.8.2001, Hans Zaunere wrote:
>sort of thing. Would it be better to just switch to TCP/IP sockets?
>
> > > my $dbh = connect("DBI:mysql:database:localhost", "user", "password");
Well it seems like you ARE using INET TCP/IP sockets, since there is
'localhost' there (which go
> Connect() does that for you.
> The mysql library handles the communication to the server.
> You just use the supplied functions.
> Are you sure it was sockets you were running out of?
Well the supplied functions have been used. How could I confirm that the system was
in fact running
out of so
Connect() does that for you.
The mysql library handles the communication to the server.
You just use the supplied functions.
Are you sure it was sockets you were running out of?
Hans Zaunere wrote:
> Ok. I didn't write these scripts, as they were in place when I arrived at this
>position, how
Ok. I didn't write these scripts, as they were in place when I arrived at this
position, however
from looking through them, it appears the actual connection to MySQL happens with
something like:
my $dbh = connect("DBI:mysql:database:localhost", "user", "password");
The above is a perl line.
These scripts should not be creating their own sockets.
The should be connecting to the one socket that the mysql server creates.
Hans Zaunere wrote:
> We have had a MySQL/Apache/Perl combo running fairly smoothly. However
> the other day MySQL seemingly went crazy, and brought the rest of the
We have had a MySQL/Apache/Perl combo running fairly smoothly. However
the other day MySQL seemingly went crazy, and brought the rest of the
system down; no sockets were available, even to ssh into. After a few
minutes, enough sockets were available to ssh into, however MySQL seemed
to far gon
