The installer replaces ~/.my.cnf without first backing it up. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Border relations between Canada and Mexico have never been better. -- George W Bush
Rick Welykochy <rick@praxis.com.au> wrote:
The installer replaces ~/.my.cnf without first backing it up.
installer.pl calls backupmycnf() and restoremycnf() at the right times, as far as I can tell. Can you tell why they are not backing up your ~/.my.cnf? Puzzled, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
MJ Ray wrote:
Rick Welykochy <rick@praxis.com.au> wrote:
The installer replaces ~/.my.cnf without first backing it up.
installer.pl calls backupmycnf() and restoremycnf() at the right times, as far as I can tell. Can you tell why they are not backing up your ~/.my.cnf?
My badness, in jumping to the wrong conclusion. This is what happened. I was at the database part of the install, creating the Koha database. The connection to mysql failed (see email regarding "Installation bug regarding creating Koha database" using IP 10.11.12.1 ... which has been submitted to tge Koha bugs database). I left the script running at that point (Ctrl C did not stop it) and entered another shell. At that point, .my.cnf was changed to a temporary copy. I wrongly concluded that the original was lost. When I terminated the install script with kill, the cleanup did restore .my.cnf. Sorry to raise this on the Koha user's list. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Border relations between Canada and Mexico have never been better. -- George W Bush
participants (2)
-
MJ Ray -
Rick Welykochy