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.

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

OS X's com.prey.agent.plist slows system shutdowns (HS:plist) #75

Closed
ghost opened this issue Jan 20, 2015 · 3 comments
Closed

OS X's com.prey.agent.plist slows system shutdowns (HS:plist) #75

ghost opened this issue Jan 20, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Jan 20, 2015

Problem

According to a user,

After installing prey to my macbook (Mavericks 10.9.5) I have started experiencing slow shutdowns. Further investigation pointed to the following setting in /Library/LaunchDaemons/com.prey.agent.plist. There there is parameter that sets exit timeout to the value 20. If I remove the plist file I have normal shutdown times, back to 2 seconds as before, and if I put it back the delay re-occurs. What exactly is that for and why the need to slow the shut own? Can I safely remove that specific parameter or set it to some lower value?

The stable version was 1.3.4 at the time.

How it was detected

User report.

Suggested solution

Reduce the shutdown time, or confirm that the problem isn't caused by Prey.

References

@tomas
Copy link
Contributor

tomas commented Jan 20, 2015

20 is the default ExitTimeout for all OSX daemons. From the original documentation:

ExitTimeOut <integer>
     The amount of time launchd waits before sending a SIGKILL signal. The default value is 20 seconds. The
     value zero is interpreted as infinity.

So, basically, something's preventing a clean shutdown which causes launchd to wait 20 seconds before killing the process by force. I suspect that this may be related to 19607b8 so I would suggest the user to upgrade to the latest version before modifying anything. Also, we should try to reproduce the error before accepting this as as a valid bug.

@ghost
Copy link
Author

ghost commented Jan 22, 2015

Version 1.3.6 fixed the issue. I'll you know in case I get anything new.

@ghost ghost closed this as completed Jan 22, 2015
@tomas
Copy link
Contributor

tomas commented Jan 22, 2015

Bravo.

This issue was closed.
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

No branches or pull requests

1 participant