Skip to content

Conversation

@WhyNotHugo
Copy link

Always run in foreground by default. Service manager and supervisors expect services to run in foreground, so they can track the lifetime of the child process. Those that don't implement their own logic to fork daemons anyway.

For users running usbmuxd manually, running in background by default provides a confusing experience, since it gives the impression that usbmuxd has exited immediately.

Anyone needing to run usbmuxd in background can use the --background option.

@WhyNotHugo WhyNotHugo mentioned this pull request Nov 25, 2023
Always run in foreground by default. Service manager and supervisors
expect services to run in foreground, so they can track the lifetime of
the child process. Those that don't implement their own logic to fork
daemons anyway.

For users running usbmuxd manually, running in background by default
provides a confusing experience, since it gives the impression that
usbmuxd has exited immediately.

Anyone needing to run usbmuxd in background can use the --background
option.
@WhyNotHugo
Copy link
Author

Gentle bump

@WhyNotHugo
Copy link
Author

The main intent here is to avoid situations where one runs usbmuxd on a terminal, and the impression is that nothing happens or that it exited immediately.

Scenarios which want the service to background itself can request this explicitly (and these scenarios are usually scripts anyway).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant