-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Added support for running services fully backgrounded on macOS #13510
Added support for running services fully backgrounded on macOS #13510
Conversation
# necessarily if it should run in a specific session type. Like database services could run with ProcessType | ||
# Interactive so they have no resource limitations enforced upon them, but they aren't really interactive in the | ||
# general sense. | ||
base[:LimitLoadToSessionType] = %w[Aqua Background LoginWindow StandardIO System] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should StandardIO
and System
be here too? In what situation would those be applicable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well I noticed in lib/service/system.rb
that you may also return the system
domain instead of a user one. So the System
type would enable you to keep using that.
As for StandardIO
: that should be used if you run something without even a GUI session being available somewhere. Like logging in to an Aqua session and then starting a service through SSH would give Background
, but rebooting your Mac and SSHing in before even logging in to Aqua should give you StandardIO
. It might be an old flag though because in my tests I always got Background
and never StandardIO
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pending CI passing on Homebrew/homebrew-services#485
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's give this a go. Any maintainer should feel free to quickly revert on a single user report with an issue.
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?This is the second part of a two-part contribution, with the first one being here. All the important info can be found there too. =] The existing automated tests should already cover the changes, although I did have to update the
expect()
stuff.