Re: [FC3] MySQL TCP/IP Config

From: Alexander Dalloz (ad+lists_at_uni-x.org)
Date: 02/10/05

  • Next message: jim lawrence: "Re: Advanced configuring of metacity [no more sawfish in FC3] or other WMs"
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    Date: Thu, 10 Feb 2005 21:04:48 +0100
    
    
    
    

    Am Do, den 10.02.2005 schrieb Øyvind Lode um 17:47:

    > Can someone please tell me what I need to do in my /etc/my.cnf or can I
    > just forward tcp 3306 to the server and it will work?
    >
    > -Øyvind

    By default the Fedora Core setup of MySQL allows both UNIX socket
    connections on the host itself as well TCP socket connections through
    port 3306, either locally (localhost) or remotely (servername:3306).

    I do not understand what you think you need to forward. Did you or your
    users read the phpMyAdmin setup documentation? The main configuration
    file contains:

    $cfg['Servers'][$i]['host'] = 'localhost'; // MySQL hostname or
    IP address
    $cfg['Servers'][$i]['port'] = ''; // MySQL port -
    leave blank for default port
    $cfg['Servers'][$i]['socket'] = ''; // Path to the
    socket - leave blank for default socket
    $cfg['Servers'][$i]['connect_type'] = 'tcp'; // How to connect to
    MySQL server ('tcp' or 'socket')

    which I feel is pretty self explanatory. If the MySQL server runs on the
    same host as the Apache with phpMyAdmin it is sufficient to use
    localhost and socket. If the MySQL server is a different host you will
    have to use the server's hostname or IP and tcp for the connect_type
    setting. You can leave the port setting off if you didn't change the
    default port 3306 to something different.

    Btw. the MySQL documentation contains the information to bind the server
    to a specific port:

    http://sunsite.mff.cuni.cz/MIRRORS/ftp.mysql.com/doc/en/Option_files.html

    Alexander

    -- 
    Alexander Dalloz | Enger, Germany | new address - new key: 0xB366A773
    legal statement: http://www.uni-x.org/legal.html
    Fedora GNU/Linux Core 2 (Tettnang) on Athlon kernel 2.6.10-1.9_FC2smp 
    Serendipity 20:54:01 up 13 days, 22:24, load average: 0.12, 0.54, 0.59 
    
    

    
    

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    


  • Next message: jim lawrence: "Re: Advanced configuring of metacity [no more sawfish in FC3] or other WMs"

    Relevant Pages

    • RE: call is blocked in recvfrom() and no further proceedings in Win CE
      ... In windows CE, I'm able to send a request but I'm unable to receive it. ... Create another socket & bind with server IP address. ... > My program has to send request to service through port 5070(in this port only ...
      (microsoft.public.windowsce.embedded)
    • Re: ipfw and nmap
      ... > even be correct but I have a bsd box that is simply providing me SSH ... add allow tcp from any to me 22 setup in via fxp0 keep-state ... Note too that there is nothing to prevent port scanners simply setting ... the 'SYN' flag in the probe packets they send to your server. ...
      (freebsd-questions)
    • Re: network programming: how does s.accept() work?
      ... The articles and books I've read all claim that the server ... port 5053 is a 'listening' port only. ... the server creates a new socket for communication between the client ... on the network, and in the RFCs which define the TCP protocol (UDP too, but ...
      (comp.lang.python)
    • Re: Detecting when a socket has been closed.
      ... shutdown the server closing the socket the client still thinks the socket is open. ... First send will not throw exception, because there is no way for TCP stack to know that other end has actually closed its receiving side. ... It takes some time for packet to reach other side and return information that server side is gone. ... in case other end has closed socket and network is still operating after first send TCP RST segment will be returned to TCP stack notifying it connection has gone down. ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: SQL 2008 Remoteverbindung
      ... Ich kann mich jetzt auf den Server verbinden & es funktioniert wirklich ... die Grundsätzliche Verbindung funktioniert jetzt. ... Bei IPALL bist du schon richtig, den Port must du aber bei 'TCP Port' ...
      (microsoft.public.de.sqlserver)