MySQL server exits
in [Slackware]
|
Prev: VI File Manager -- Vifm -update
Next: IBM R51 +Slack12
From: Richard James on 29 Mar 2008 06:23 On Sat, 29 Mar 2008 09:53:06 +1000, Res wrote: > On Sat, 28 Mar 2008, Richard James wrote: > > >> Actually that is incorrect run mysql_install_db as the mysql user and >> you don't have to change any permissions. >> >> Richard James > > What, you allow daemon accounts to have a valid shell? *shakes head* I didn't set the default, that is Slackware 12's default. Maybe you should take this up with Pat? Richard James -- sig fail on line -1
From: Richard James on 29 Mar 2008 07:07 On Fri, 28 Mar 2008 18:14:10 -0500, Dave Uhring wrote: > You are indeed correct in that Slackware has introduced an unnecessary > security vulnerability by giving the mysql user a workable shell. I had > not noticed that before. > > usermod -s /bin/false mysql After that has been done you can install the mysql database like this mysql_install_db --user=mysql It does not change the group of the database but as far as I can tell access works as normal. Richard James -- sig fail on line -1
From: Thats Mr Goblin on 29 Mar 2008 22:31 On 2008-03-28, Dave Uhring <daveuhring(a)yahoo.com> wrote: > >> So it's likely someone building a package missed the file >> trying to run around the normal mysql_install_db script. > > Nobody missed anything in the packaging; Slackware has always required > that mysql_install_db be run prior to using mysql. > > The reason is quite simply understood. Slackware ships with packages made > from unaltered sources and building mysql source does not result in the > generation of the initial database set. The main reason is so that nobody gets the nasty surprise of having their databases overwritten during the upgrade/installation of the MySQL package. There also exists a mysql_secure_installation script that I find helpful during setup of MySQL. -- "Dad, how much does it cost to get married?" "I don't know son .... I'm still paying."
From: Dave Uhring on 29 Mar 2008 22:41 On Sun, 30 Mar 2008 02:31:38 +0000, Thats Mr Goblin wrote: > The main reason is so that nobody gets the nasty surprise of having > their databases overwritten during the upgrade/installation of the > MySQL package. Are there any serious people who fail to backup their databases before upgrading? > There also exists a mysql_secure_installation script that I find helpful > during setup of MySQL. I've been using mysql for about 7 years and never had a need for it - didn't even know it was there :>
From: Thats Mr Goblin on 29 Mar 2008 23:25
On 2008-03-30, Dave Uhring <daveuhring(a)yahoo.com> wrote: > On Sun, 30 Mar 2008 02:31:38 +0000, Thats Mr Goblin wrote: > >> The main reason is so that nobody gets the nasty surprise of having >> their databases overwritten during the upgrade/installation of the >> MySQL package. > > Are there any serious people who fail to backup their databases before > upgrading? I'd have to agree but you'd be surprised at the number of people that complain about this sort of thing.. the index.html file in the httpd package is a perfect example. (and that file does ship with the source) >> There also exists a mysql_secure_installation script that I find helpful >> during setup of MySQL. > > I've been using mysql for about 7 years and never had a need for it - > didn't even know it was there :> It's relatively new (to us old fogies at least) but it's there and does the job well. -- "Dad, how much does it cost to get married?" "I don't know son .... I'm still paying." |