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

Addition to Step 4: Things that can block reboot #2

Open
madc opened this issue Mar 10, 2014 · 2 comments
Open

Addition to Step 4: Things that can block reboot #2

madc opened this issue Mar 10, 2014 · 2 comments

Comments

@madc
Copy link

madc commented Mar 10, 2014

There are some edge-cases, that can prevent a machine from rebooting automatically. Here are two, that i encountered during a recent project when using the "Schedule" option.

  1. Review running processes
    Screenshot
    I have only the german screenshot and couldn't find the English translation. In my case, this message appeared, as i had a simple bash script periodically checking some stuff.

  2. "There are currently logged in users who may lose unsaved changes if you restart this computer."
    Screenshot
    If you use some share (smb/afp) to sync/update files, you have to manually disconnect from the machine, otherwise this message will block the reboot.

This is just a quick draft, so i won't forget to post this here. Will be improved as soon as possible. Support and discussion appreciated!

@laserpilot
Copy link
Owner

Ah yeah - I've caught these before - it also happens if you are screen shared into an installation computer, it will warn you other users are connected - I haven't investigated what you can do to force reboot in those situations - you would probably need some kind of shell script that is a backup or something

  1. Shutdown immediately
    sudo halt
  2. Restart immediately
    sudo reboot
  3. Shutdown in 10 minutes
    sudo shutdown -h +10
  4. Shutdown at 8 pm
    sudo shutdown -h 20:00
  5. Shutdown immediately
    sudo shutdown -h now
  6. Reboot immediately
    sudo shutdown -r now

@madc
Copy link
Author

madc commented Mar 10, 2014

I've to look up how i solved this issue, but as you said, i had to write some shell script. Those are quite annoying messages as there is no solution to get rid of them when using the "Schedule..."

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

2 participants