On Fri, Feb 13, 2015 at 11:31 AM, Murray Eisenberg
murrayeisenb...@gmail.com wrote:
I've never heard permission +x referred to as search permission. I
thought +x is execute permission, which is surely more dangerous than +r
read permission.
How do you execute a directory? +x *on
OK, understood. But still, it seems a security risk to use chmod a+x or even
chmod o+x on each of the directories /Volumes, /Volumes/MacHD,
/Volumes/MacHD/Users, /Volumes/MacHD/Users/thisuser,
/Volumes/MacHD/Users/thisuser/mysql (leading to
/Volumes/MacHD/Users/thisuser/mysql/data, which is
On Fri, Feb 13, 2015 at 12:05 PM, Murray Eisenberg
murrayeisenb...@gmail.com wrote:
Isn't there some safer way to be able to use mysql with a datadir in a
non-default location (after specifying it in my.cnf, of course)?
You can use ACLs to only grant that permission to the _mysql user (see
I've never heard permission +x referred to as search permission. I thought
+x is execute permission, which is surely more dangerous than +r read
permission.
On 13 Feb2015, at 12:19 AM, Brandon Allbery allber...@gmail.com wrote:
On Fri, Feb 13, 2015 at 12:10 AM, Murray Eisenberg
On Fri, Feb 13, 2015 at 12:10 AM, Murray Eisenberg
murrayeisenb...@gmail.com wrote:
Do I also need to give the group _mysql read permission to some or all of
/Volumes, /Volumes/MacHD, /Volumes/MacHD/Users,
/Volumes/MacHD/Users/thisuser, /Volumes/MacHD/Users/thisuser/mysql ?
If so, might
On Fri, Feb 13, 2015 at 12:43 PM, Murray Eisenberg
murrayeisenb...@gmail.com wrote:
(I find it strange that while searching on-line for how to use a
non-default location for the mysql datadir, none of them mentioned such ACL
manipulation (all they described was giving _mysql ownership of the
On Fri, Feb 13, 2015 at 12:34 PM, Murray Eisenberg
murrayeisenb...@gmail.com wrote:
The Finder Get Info Sharing Permissions doesn't seem to allow adding x
permission to anything, just read only, write only, or read write. In any
case, user _mysql does not appear among the users to add that
On Feb 12, 2015, at 5:24 PM, Murray Eisenberg murrayeisenb...@gmail.com wrote:
I should add that whereas the command sudo port load mysql56-server runs
without returning any error to the terminal, the next command, beginning
/opt/local/lib/mysql56/bin/mysql bombs out, returning the error:
On Feb 12, 2015, at 5:24 PM, Murray Eisenberg murrayeisenb...@gmail.com wrote:
I should add that whereas the command sudo port load mysql56-server runs
without returning any error to the terminal, the next command, beginning
/opt/local/lib/mysql56/bin/mysql bombs out, returning the error:
Since I cannot get mysql server to run, from
/opt/local/lib/mysql56/bin/mysqladmin variables | grep socket
I obtain output:
/opt/local/lib/mysql56/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
I don't think I have another my.cnf. I see:
/opt/local/lib/mysql56/bin/mysqld --help --verbose 21 | grep -A 1 Default
options | tail -n +2
/etc/my.cnf /etc/mysql/my.cnf /opt/local/etc/mysql56/my.cnf ~/.my.cnf
However, in /etc (actually, /private/etc) there's a file my.cnf~ but _no_
On Fri, Feb 13, 2015 at 3:46 PM, William H. Magill mag...@mac.com wrote:
I have no statistics, but when I retired back in 2003, almost nobody used
ACLs even though they had been around for several years. Looking at the ACL
man page, it appears that BSD included them in 2002. . . . and just
On Fri, 13 Feb 2015, Brandon Allbery wrote:
I've never heard permission +x referred to as search
permission. I thought +x is execute permission, which is
surely more dangerous than +r read permission.
How do you execute a directory? +x *on directories* is search.
ACLs are not common knowledge -- Apple probably uses them more than any other
vendor.
While ACLs (Access Control Lists) provide much finer-grained security than the
old User/Group/Other (or Owner/Group/World depending on your background)
technique, they take a great deal more THOUGHT and
Thanks to repeated help from Ryan Schmidt and Brandon Allbery, I finally was
able to get mysql56 to work with a non-default datadir location. Here's what I
did:
0. Uninstalled the macports mysql56-server and
deleted both /opt/local/var/db/mysql56 and
On Feb 13, 2015, at 12:38 PM, Murray Eisenberg murrayeisenb...@gmail.com
wrote:
Since I cannot get mysql server to run, from
/opt/local/lib/mysql56/bin/mysqladmin variables | grep socket
I obtain output:
/opt/local/lib/mysql56/bin/mysqladmin: connect to server at 'localhost'
CORRECTION: The command I use to start the mysql server is indeed the one for
the Macports version, namely:
sudo /opt/local/share/mysql56/support-files/mysql.server start
(Sorry for the typo.)
On 12 Feb2015, at 5:05 PM, Murray Eisenberg murrayeisenb...@gmail.com wrote:
After upgrading
I should add that for the (re)installation of mysql56, I followed all the steps
at https://trac.macports.org/wiki/howto/MySQL with one change: instead of using
load to start the server, I'm using mysql.server start.
On 12 Feb2015, at 5:05 PM, Murray Eisenberg murrayeisenb...@gmail.com wrote:
That wasn't the issue. The issue is that the server won't start after I changed
to matador.
(mysql.server is just a convenient script to start or stop mysql; it reads
datadir, among other things, from my.cnf).
On 12 Feb2015, at 6:48 PM, Bradley Giesbrecht pixi...@macports.org wrote:
I am
I am not familiar with mysql.server but using the mysql56-server port to start
and stop mysqld works as expected:
sudo port install mysql56-server
sudo port load mysql56-server
/opt/local/lib/mysql56/bin/mysql -S /opt/local/var/run/mysql56/mysqld.sock
-uroot -p -e 'show variables like datadir;'
I should add that whereas the command sudo port load mysql56-server runs
without returning any error to the terminal, the next command, beginning
/opt/local/lib/mysql56/bin/mysql bombs out, returning the error:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
On Feb 12, 2015, at 4:05 PM, Murray Eisenberg wrote:
After upgrading from OS X Mavericks to Yosemite, I did the standard procedure
for migrating macports. But I found that the mysql server would not start. So
I uninstalled mysql56 completely and installed anew. Worked just fine.
But, I
User _mysql owns /Volumes/MacHD/Users/thisuser/Databases/mysql/data. And also
everything within that directory.
Do I also need to give the group _mysql read permission to some or all of
/Volumes, /Volumes/MacHD, /Volumes/MacHD/Users, /Volumes/MacHD/Users/thisuser,
On Fri, Feb 13, 2015 at 12:10 AM, Murray Eisenberg
murrayeisenb...@gmail.com wrote:
Do I also need to give the group _mysql read permission to some or all of
/Volumes, /Volumes/MacHD, /Volumes/MacHD/Users,
/Volumes/MacHD/Users/thisuser, /Volumes/MacHD/Users/thisuser/mysql ?
I would hope
After upgrading from OS X Mavericks to Yosemite, I did the standard procedure
for migrating macports. But I found that the mysql server would not start. So I
uninstalled mysql56 completely and installed anew. Worked just fine.
But, I want my datadir to be someplace else from the default, so I
25 matches
Mail list logo
