On Aug 17, 2007, at 22:10, Tabitha McNerney wrote:
On 8/16/07, Ryan Schmidt wrote:
On Aug 16, 2007, at 08:22, Tabitha McNerney wrote:
> I noticed that the MySQL 5 MacPort re-uses the "mysql" user account
> that is already a part of Mac OS X. I am wondering if it might be
> better to create a separate user account such as "mysql5" rather
> than re-use Apple's "mysql" user account? I guess its unlikely that
> Apple would change the MySQL user account that is packaged with Mac
> OS X but for a more independent approach for MacPorts, wouldn't it
> make more sense to have a separate account?
What benefit would that have?
I remember that Apple added the "mysql" user in Mac OS X 10.2
precisely because so many people wanted to use MySQL on Mac OS X.
I don't think they're going to remove it again. It would break too
many
people.
I see your logic but I also wouldn't put it past Apple to change
something (for whatever reason they may come up with in-house). I
just thought it might be prudent to parallel the PostgreSQL
MacPorts which also create their own user accounts to keep things
separate from what Apple might do with its sole control.
If Apple does change or remove the mysql account, then we can modify
the mysql portfiles as needed. But until then, I'm inclined not to
fix something that ain't broke.
The other thing that concerns me is that the Apple-supplied MySQL
user ("mysql") is initialized with a crypt password. Crypt should
really be deprecated into the rear view mirror and replaced with
MD5 true? Anyway, just some food for thought.
I have no information on that topic. If you believe the configuration
of the Apple-supplied mysql account is bad in some way, you should
take it up with Apple.
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users