List:General Discussion« Previous MessageNext Message »
From:Paul DuBois Date:June 13 2001 8:22pm
Subject:Re: my.cnf mystery
View as plain text  
At 2:30 PM -0400 6/13/01, Dennis wrote:
>At 08:30 PM 06/12/2001, Philip Mak wrote:
>>[client]
>>port=3306
>>socket=/home/mysql/mysql.sock
>>
>>[mysqld]
>>port=3306
>>socket=/home/mysql/mysql.sock
>
>
>here are examples of variables that you could not deduce from using 
>--help. the "socket" one,for example, was one that I asked about 
>last week, when the consensus answer was to use a link to change 
>this. Clearly the my.cnf route is a better choice.
>
>Dennis

Perhaps this will be considered nitpicking, but ...

1) socket isn't a variable.  It's a parameter.  Variable are those things
    that are set with set-variable=varname=value.

2) my.cnf is not clearly a better choice.  For programs that don't consult
    option files, it won't work.

-- 
Paul DuBois, paul@stripped
Thread
Installation Problemsales29 May
  • my.cnf mysteryDennis12 Jun
    • Re: my.cnf mysteryPaul DuBois12 Jun
      • Re: my.cnf mysteryWilliam M. Quarles12 Jun
        • Re: my.cnf mysteryPaul DuBois12 Jun
          • Re: my.cnf mysteryWilliam M. Quarles13 Jun
            • Re: my.cnf mysteryPhilip Mak13 Jun
              • Re: my.cnf mysteryWilliam M. Quarles13 Jun
              • Re: my.cnf mysteryDennis13 Jun
                • Re: my.cnf mysteryPaul DuBois13 Jun
            • Re: my.cnf mysteryPaul DuBois13 Jun
              • Re: my.cnf mysteryquarlewm13 Jun