On Thu, May 26, 2011 at 10:22 AM, Andreas Petzold <[log in to unmask]> wrote: > On Thursday, May 26, 2011 16:03:31 Stefan Eriksson wrote: >> torsdagen den 26 maj 2011 14.38.32 skrev du: >> > Hi, >> > >> > On Thursday, May 26, 2011 14:03:06 Stefan Eriksson wrote: >> > > Hi I've just now installed a minimal installation but still there is a >> > > file called /etc/my.cnf >> > > >> > > ls -l /etc/my.cnf >> > > -rw-r--r--. 1 root root 251 20 jan 23.36 /etc/my.cnf >> > > >> > > I have never installed mysql-server on this system. >> > >> > you can ask RPM which package this file belongs to: >> > >> > rpm -qf /etc/my.cnf >> > >> > If the file doesn't belong to an RPM, it gets a little tricky. >> > >> > Cheers, >> > >> > Andreas >> >> Thanks seems like mysql-libs-5.1.52-1.el6_0.1.x86_64 >> >> rpm -qf /etc/my.cnf >> mysql-libs-5.1.52-1.el6_0.1.x86_64 >> >> I'm guessing this is installed per default. > > there's no need to guess :-) . Simply run > > repoquery --whatrequires mysql-libs > > and it will tell you which installed RPMs require mysql-libs. If nothing comes > up, then you either explicitly requested the RPM or it is in the default list > of packages. > > repoquery is provided by the yum-utils package. So is "rpm -q --whatrequires mysql-libs" and "rpm -q --whatrequires /etc/my.cnf". Unfortunately, MySQL has that !@#$!@$#@ file hardcoded. So even if you want to put your specific settings such as port numbers and database locations somewhere else and write a config file for it, the binaries *INSIST* on looking at /etc/my.cnf. This makes one database server tuning /etc/my.cnf very risky to any other MySQL databases on this host, even with their own init scripts and config files and databases. Drove me *NUTS* a few years back when testing parallel configurations before deployment....