-
-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start services - "The UserName key is not supported for non-System services." #56
Comments
I'm also on 10.11.5 and am not able to reproduce this. The |
Running it manually works. This gets weirder and weirder. |
@daFish I'm afraid this doesn't look like a Homebrew issue. If you can figure out a fix and create a PR then we'll consider it. Sorry! |
Thanks, @MikeMcQuaid. I try to come up with a solution. However, I have the exact same issue on another machine running 10.11.5. |
@daFish Try to remove the |
@MikeMcQuaid Still doesn't work. The |
Starting the service with |
@daFish You may also want to try and remove the relevant |
also CC @ilovezfs for thoughts. |
Perhaps they got stricter and made the incorrect usage an error instead of just ignoring it. As a workaround, @daFish can you try opening brew-services.rb, and changing
to
|
@ilovezfs This worked and I was able to start the services without any problems. |
Cool. You may want to commit that change for now, since brew update will try to stash it otherwise.
|
@MikeMcQuaid Sure. Let's go with that as a workaround, clean up the formulae, and then drop the section entirely. |
@ilovezfs Sounds good. |
This will avoid setting the key inappropriately, but will also continue to prevent "legitimate" use of the key (e.g., setting UserName "php" for a daemon). Closes Homebrew#56.
@MikeMcQuaid Done. |
Since upgrading to OS X 10.11.5 I can no longer start services like httpd22.
brew services start httpd22
results in==> Successfully started``httpd22``(label: homebrew.mxcl.httpd22)
which is perfectly fine.However, when inspecting the logs using
syslog -k Sender com.apple.xpc.launchd
I noticed the following entries:The
.plist
-file contains the section in question which was perfectly fine prior the update. Anyone experienced anything like that before?The text was updated successfully, but these errors were encountered: