Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Restart required for deleted variables #11

Closed
dwinfield opened this issue Jun 17, 2015 · 2 comments
Closed

Restart required for deleted variables #11

dwinfield opened this issue Jun 17, 2015 · 2 comments
Labels
bug

Comments

@dwinfield
Copy link

Although changes to the variables are picked up when an app using that variable is restarted, if a variable is deleted, a restart of the computer is required.
@hschmidt
Copy link
Owner

hschmidt commented Jan 1, 2017

I can reproduce this.

@hschmidt hschmidt added the bug label Jan 1, 2017
@hschmidt
Copy link
Owner

hschmidt commented Jan 3, 2017

This happens on 10.10 and newer where a reimplementation of launchd breaks the unsetenv functionality. The corresponding API still exists in the reimplementation, and I assume attempts to emulate the legacy implementation; but evidently it is broken. Interestingly, launchctl unsetenv works because it isn't using the emulated legacy API but the new XPC-based API. To fix we need to reverse-engineer the new API—it is undocumented—and use it instead of relying on the emulation.

hschmidt added a commit that referenced this issue Jan 4, 2017
@hschmidt
Fix: Can’t unset variables with legacy API (connected to #11)
411da8d 
Regression introduced in 3c4f0fc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hschmidt @dwinfield