That depends where you install mysql, with the packages from ubuntu
repositories it's located in /etc/mysql.
I think the "grant all ....." line is useless, the best thing (and most
easy) is to ask to users to use root user. Here how I see things :
step 1 : install mysql
step 2 : open my.cnf file (in mysql root directory if installed by hand or
in /etc/mysql/ if installed with ubuntu packages)
step 3 : add these parametesr in the [mysqld] section to have the utf8
encoding by default :
character-set-server=utf8
skip-character-set-client-handshake
step 4 : change max_allowed_packet=16M to max_allowed_packet=1G
step 5 : change key_buffer=16M to key_buffer=1G
===> "key_buffer_size" parameter is now deprecated, use "key_buffer"
instead.
step 6 : change query_cache_size=16M to query_cache_size=1G
These next step are made for those who installed mysql by hand :
step 7 : set socket parameter to "$MYDIR/mysqld.sock"
====> now it's mysqld.sock and not mysql.sock
step 8 : set datadir parameter to "$MYDIR/data"
step 9 : open your ~/.bashrc file to add : export
MYDIR=/path/where/you/installed/mysql
What do you think ?
Best.
Julien.
2013/4/16 Andrea Di Menna <[email protected]>
> Actually MySQL should be looking for configuration files in different
> locations
>
>
> http://dev.mysql.com/tech-resources/articles/mysql_intro.html#SECTION0001500000
>
> Cheers
> Andrea
> Il giorno 16/apr/2013 20:24, "Julien Plu" <
> [email protected]> ha scritto:
>
> Yes I think it's the best idea, and I think too that mysql is configured
>> only by the "/etc/mysql/my.cnf" file.
>>
>> Best.
>>
>> Julien.
>>
>>
>> 2013/4/16 Jona Christopher Sahnwaldt <[email protected]>
>>
>>> On 16 April 2013 19:56, Julien Plu <[email protected]>
>>> wrote:
>>> > As you wish, it's just a standard configuration with 3-4 modifications
>>> > nothing more.
>>> > But at least I can precise in the guide the parameters that
>>> > they must change ?
>>>
>>> Just copy the parameters used in mysql.sh to the config file, without
>>> the leading '--'. Thus:
>>>
>>> mysql.sh:
>>>
>>> ./bin/mysqld_safe --no-defaults --character-set-server=utf8
>>> --socket="$MYDIR/mysql.sock" --bind-address=localhost
>>> --datadir="$MYDIR/data" --max_allowed_packet=1G --key_buffer_size=1G
>>> --query_cache_size=1G >>"$MYDIR/mysql.log" 2>&1 &
>>>
>>> config file:
>>>
>>> socket="$MYDIR/mysql.sock"
>>> bind-address=localhost
>>> character-set-server=utf8
>>> datadir="$MYDIR/data"
>>> max_allowed_packet=1G
>>> key_buffer_size=1G
>>> query_cache_size=1G
>>>
>>> Maybe that works, I don't know. Maybe you have to replace '-' by '_'.
>>> Or maybe the names are actually different.
>>>
>>> Also, I don't remember what no-defaults does and if should be in a
>>> config file.
>>>
>>> I think MySQL uses different config files for client and server, so
>>> you may have to edit them both.
>>>
>>> JC
>>>
>>> >
>>> > And I think you right for (at least) your LocalSettings.php because it
>>> > doesn't work with me :-( And I have to test the solution from Dimitris.
>>> >
>>> > Best.
>>> >
>>> > julien.
>>> >
>>> >
>>> > 2013/4/16 Jona Christopher Sahnwaldt <[email protected]>
>>> >>
>>> >> The problem with having a whole configuration file in the repo is that
>>> >> the file probably contains many other settings besides the ones we
>>> >> need, and it changes with each MySQL version. When we use command line
>>> >> parameters, we don't have to change any MySQL config files, we just
>>> >> add the three or four settings that we need, and they don't change
>>> >> between MySQL versions.
>>> >>
>>> >> Maybe there is a way to tell MySQL, "here's an addtional config file
>>> >> whose settings should override the ones in the main config file". Then
>>> >> we could check in a minimal config file with just our settings. But
>>> >> taking a large config file from a MySQL installation, changing a few
>>> >> lines and then putting the modified version into the repo leads to
>>> >> more problems than it solves.
>>> >>
>>> >> We have the same problem with MediaWiki: we once took
>>> >> LocalSettings.php and ApiParse.php from a MediaWiki installation,
>>> >> modified a few lines and put the whole files into our repo. But in
>>> >> newer versions, the files look quite different, and the versions from
>>> >> our repo just don't work. Users have to edit the files and add the
>>> >> stuff needed for the abstract extractor.
>>> >>
>>> >> Cheers,
>>> >> JC
>>> >>
>>> >> On 16 April 2013 15:39, Julien Plu <
>>> [email protected]>
>>> >> wrote:
>>> >> > Ok thank you :-)
>>> >> >
>>> >> > I finish all the extraction process, and after I will modify the
>>> guide
>>> >> > to
>>> >> > include what I think is missing. For the conf file I will make a
>>> pull
>>> >> > request with mine if everything is ok during all the process.
>>> >> >
>>> >> > Best.
>>> >> >
>>> >> > Julien.
>>> >> >
>>> >> >
>>> >> > 2013/4/16 Dimitris Kontokostas <[email protected]>
>>> >> >>
>>> >> >> Hi Julien,
>>> >> >>
>>> >> >> You are free to improve any page on our wiki :)
>>> >> >>
>>> >> >> Regarding the MySQL script, if you think a conf file is easy to
>>> create
>>> >> >> and
>>> >> >> use, you can make a pull request and we 'll make the necessary
>>> tests.
>>> >> >>
>>> >> >> Best,
>>> >> >> Dimitris
>>> >> >>
>>> >> >>
>>> >> >> On Tue, Apr 16, 2013 at 1:14 PM, Julien Plu
>>> >> >> <[email protected]> wrote:
>>> >> >>>
>>> >> >>> Ok so if I have your approval I will modify the step-by-step
>>> guide.
>>> >> >>>
>>> >> >>> And maybe instead of using a script we can put a copy of a mysql
>>> >> >>> configuration file that users must have, no ? Less work (you don't
>>> >> >>> have a
>>> >> >>> script to maintain) and more easy for users. What do you think ?
>>> >> >>> Unless
>>> >> >>> there is a minimal or maximal version of mysql to use ?
>>> >> >>>
>>> >> >>> Best.
>>> >> >>>
>>> >> >>> Julien.
>>> >> >>>
>>> >> >>>
>>> >> >>> 2013/4/16 Jona Christopher Sahnwaldt <[email protected]>
>>> >> >>>>
>>> >> >>>> PS: It would be cool if you could add a few lines to
>>> >> >>>>
>>> >> >>>>
>>> >> >>>>
>>> https://github.com/dbpedia/extraction-framework/wiki/Dbpedia-Abstract-Extraction-step-by-step-guide
>>> >> >>>> or even improve the script itself with better error and usage
>>> >> >>>> messages
>>> >> >>>> and send a pull request.
>>> >> >>>>
>>> https://github.com/dbpedia/extraction-framework/wiki/Contributing
>>> >> >>>> Thanks!
>>> >> >>>>
>>> >> >>>> On Apr 16, 2013 12:02 PM, "Jona Christopher Sahnwaldt"
>>> >> >>>> <[email protected]>
>>> >> >>>> wrote:
>>> >> >>>>>
>>> >> >>>>> I quickly put that script together when I ran the abstract
>>> >> >>>>> extraction
>>> >> >>>>> last year, and I never expected it to have so many users. :-)
>>> >> >>>>>
>>> >> >>>>> I'm sorry that it's so badly documented and not really finished.
>>> >> >>>>> I'll
>>> >> >>>>> improve it in May. Don't have time now. :-(
>>> >> >>>>>
>>> >> >>>>> JC
>>> >> >>>>>
>>> >> >>>>> aaaa ok we need to download the MySQL archive before I thought
>>> the
>>> >> >>>>> script did it for us. Maybe add this precision in the
>>> documentation
>>> >> >>>>> ?
>>> >> >>>>>
>>> >> >>>>> Thanks :-)
>>> >> >>>>>
>>> >> >>>>> Best.
>>> >> >>>>>
>>> >> >>>>> Julien.
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>> 2013/4/16 Andrea Di Menna <[email protected]>
>>> >> >>>>>>
>>> >> >>>>>> Hi Julien,
>>> >> >>>>>>
>>> >> >>>>>> reading the mysql.sh script you should first set the env
>>> variable
>>> >> >>>>>> MYSQL_HOME to you MySQL installation folder.
>>> >> >>>>>> The script is first accessing that folder and then launching
>>> some
>>> >> >>>>>> MySQL scripts/commands, link mysql_install_db [1]
>>> >> >>>>>>
>>> >> >>>>>> Cheers
>>> >> >>>>>> Andrea
>>> >> >>>>>>
>>> >> >>>>>> [1]
>>> http://dev.mysql.com/doc/refman/5.0/en/mysql-install-db.html
>>> >> >>>>>>
>>> >> >>>>>>
>>> >> >>>>>> 2013/4/16 Julien Plu <[email protected]>
>>> >> >>>>>>>
>>> >> >>>>>>> Hi,
>>> >> >>>>>>>
>>> >> >>>>>>> The extraction tool has finished to compile and to download
>>> the
>>> >> >>>>>>> dumps
>>> >> >>>>>>> so now I install MySQL with the "dump/src/main/bash/mysql.sh"
>>> >> >>>>>>> script, and
>>> >> >>>>>>> when I run this script with the "sudo ./src/main/bash/mysql.sh
>>> >> >>>>>>> install
>>> >> >>>>>>> /etc/mysql/" command I fall on this error :
>>> >> >>>>>>>
>>> >> >>>>>>> ./src/main/bash/mysql.sh: ligne 51:
>>> ./scripts/mysql_install_db: No
>>> >> >>>>>>> such file or directory
>>> >> >>>>>>>
>>> >> >>>>>>> And indeed this script doesn't exist in the repo. I have to
>>> >> >>>>>>> download
>>> >> >>>>>>> it somewhere ?
>>> >> >>>>>>>
>>> >> >>>>>>> Best.
>>> >> >>>>>>>
>>> >> >>>>>>> Julien.
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> ------------------------------------------------------------------------------
>>> >> >>>>>>> Precog is a next-generation analytics platform capable of
>>> advanced
>>> >> >>>>>>> analytics on semi-structured data. The platform includes APIs
>>> for
>>> >> >>>>>>> building
>>> >> >>>>>>> apps and a phenomenal toolset for data science. Developers
>>> can use
>>> >> >>>>>>> our toolset for easy data analysis & visualization. Get a free
>>> >> >>>>>>> account!
>>> >> >>>>>>> http://www2.precog.com/precogplatform/slashdotnewsletter
>>> >> >>>>>>> _______________________________________________
>>> >> >>>>>>> Dbpedia-discussion mailing list
>>> >> >>>>>>> [email protected]
>>> >> >>>>>>>
>>> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>>> >> >>>>>>>
>>> >> >>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> ------------------------------------------------------------------------------
>>> >> >>>>> Precog is a next-generation analytics platform capable of
>>> advanced
>>> >> >>>>> analytics on semi-structured data. The platform includes APIs
>>> for
>>> >> >>>>> building
>>> >> >>>>> apps and a phenomenal toolset for data science. Developers can
>>> use
>>> >> >>>>> our toolset for easy data analysis & visualization. Get a free
>>> >> >>>>> account!
>>> >> >>>>> http://www2.precog.com/precogplatform/slashdotnewsletter
>>> >> >>>>> _______________________________________________
>>> >> >>>>> Dbpedia-discussion mailing list
>>> >> >>>>> [email protected]
>>> >> >>>>> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>>> >> >>>>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> ------------------------------------------------------------------------------
>>> >> >>> Precog is a next-generation analytics platform capable of advanced
>>> >> >>> analytics on semi-structured data. The platform includes APIs for
>>> >> >>> building
>>> >> >>> apps and a phenomenal toolset for data science. Developers can use
>>> >> >>> our toolset for easy data analysis & visualization. Get a free
>>> >> >>> account!
>>> >> >>> http://www2.precog.com/precogplatform/slashdotnewsletter
>>> >> >>> _______________________________________________
>>> >> >>> Dbpedia-discussion mailing list
>>> >> >>> [email protected]
>>> >> >>> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>>> >> >>>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> Kontokostas Dimitris
>>> >> >
>>> >> >
>>> >
>>> >
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Precog is a next-generation analytics platform capable of advanced
>> analytics on semi-structured data. The platform includes APIs for building
>> apps and a phenomenal toolset for data science. Developers can use
>> our toolset for easy data analysis & visualization. Get a free account!
>> http://www2.precog.com/precogplatform/slashdotnewsletter
>> _______________________________________________
>> Dbpedia-discussion mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>>
>>
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
