Ticket #13705 (closed enhancement: fixed)
mysql5 should use _mysql user in Leopard
| Reported by: | andrejohn.mas@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.5.2 |
| Keywords: | Cc: | anton.chaplygin@…, sakutz@… | |
| Port: | mysql5 |
Description
Leopard changed some things, notably all daemon user now start with an underscore, such as _mysql, _www, _svn, etc. This ended up breaking my mysql5 installation (I did an upgrade, rather than a clean and restore). For this reason mysql5 probably needs to be modified to support this new convention.
Change History
comment:2 Changed 5 years ago by jmpp@…
- Type changed from defect to enhancement
- Milestone changed from MacPorts base bugs to Port Enhancements
comment:3 Changed 5 years ago by ryandesign@…
It seems that Tabitha predicts the future. :) (She suggested four months ago that MacPorts should make its own user account for the mysql5 portfile instead of using the system mysql account, in case Apple ever changed the system account -- which, much to my surprise, they've now done.)
comment:4 Changed 5 years ago by anton.chaplygin@…
Hi! I've got the same problem and i can't find anything about it in google. Could you tell me, please, in few words how to solve it before this ticket will be closed? Thank you.
comment:6 Changed 5 years ago by anton.chaplygin@…
Ah! Sorry for troubling. This helped me:
# chown -R _mysql /opt/local/var/run/mysql5/
comment:7 Changed 4 years ago by anonymous
- Milestone Port Enhancements deleted
Milestone Port Enhancements deleted
comment:8 Changed 4 years ago by ryandesign@…
- Cc sakutz@… added
- Status changed from new to assigned
- Port set to mysql5
Has duplicate #22472. I didn't realize this was actually causing problems -- in my testing, asking for user "mysql" on Leopard or Snow Leopard transparently became user "_mysql" so there was no problem.
comment:9 Changed 4 years ago by sakutz@…
I apologize that I didn't see that this was a duplicate. Yes, this caused issues, at least on 10.6.2. The directories were not getting the right permissions and thus the daemon was failing to start.
comment:10 Changed 4 years ago by ryandesign@…
- Status changed from assigned to closed
- Resolution set to fixed
Should be fixed by r60468.