-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update docs and launchd configuration - stdout not used #70
Comments
Merged
We may still accidentally have some output in stdout, so I suggest keeping the stdout log too. |
Ok, maybe just add a node that we log to stderr and stdout is unused. |
nirs
added a commit
to nirs/socket_vmnet
that referenced
this issue
Nov 10, 2024
- Improve instructions for enabling debug logs - Mention that stdout is not used for logging - Remove HOMEBREW_PREFIX from logs locations since homebrew installation is not recommended. - Move note about old logs location to a separate note. Fixes: lima-vm#70 Signed-off-by: Nir Soffer <[email protected]>
Merged
nirs
added a commit
to nirs/socket_vmnet
that referenced
this issue
Nov 20, 2024
- Improve instructions for enabling debug logs - Mention that stdout is not used for logging - Remove HOMEBREW_PREFIX from logs locations since homebrew installation is not recommended. - Remove note about old logs location Fixes: lima-vm#70 Signed-off-by: Nir Soffer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since #58 we log only to stderr, so /var/log/socket_vmnet/stdout is never used.
The text was updated successfully, but these errors were encountered: