Scheduled shutdown stops if there are connections

Same issue here. Really moronic to have a shut down scheduler and NOT allow shutdown. For Pete's sake Apple.. disconnect users and shut down. That's the way it's work in all previous OS versions.

For what it's worth, even if you do disconnect from the system via the remote connections, OS 10.8.1 still thinks there's a connection soemwhere. You have to disconnect from the server itself by booting all users on the LAN to get the disconnect to stop popping up the silly warning.

<sarcasm> Oh yeah... the OS just keeps getting better and better. </sarcasm>

Shutting down a file server while users are connected to it (and possibly updating files) is like unplugging a disk from your computer without dismounting its volume(s) or powering off your computer without shutting it down. You can often get away with it, but you run the risk of damaging the integrity of any files that were incompletely updated.

Disconnecting remote users then performing a scheduled shut down is no risk to file integrity. The Mac OS has ALWAYS done this it's only with OS 10.8 that the warning appears and shut down fails. In 20+ years of scheduling shutdowns on Macs I have never experienced an issue.

Well, you may know that none of the computers still connected is in the middle of updating a file, it's not clear that your home server has enough information to know that. If previous versions of the system allowed shutdown in that case and caused data loss, it could well have been reported as a bug and been fixed in 10.8.

cymorrow wrote:

Why can't the scheduled shutdown process, via an option check box, find out if there are no active connections, then close off the connections it thinks are still there and then do the shutdown.

How do you define what makes an existing connection "active"? Just because the compter at the other end is sleeping, that doesn't mean that it doesn't have any files open. If a computer has a file open, it might awake at any moment and start using the file. Again, you may know that won't happen, but how does the file server code protect against it?

Here the thing.. what happens when the user clicks the "shut down" button in the warning? The answer.. exactly what should happen without the warning. Users are disconnected and then the shut down processes intiated.

All the moumbo jumbo about data loss etc. is just panic-talk. If a file transfer is actually in progress the OS knows it and therefore prevents shutdown (and disconnect). It's VERY clear that markwmsnhas no clue what he's posting about and is merely an Apple fanboy.

Face it, The OS gets worse and worse. This is one of those processes which has ran flawlessles since, heck OS8. Now markwmsnwants us to beleive there's a reason it no longer works as expected. He's just full of it and making excuses for things he doesn't know about.

Apple, please fix your shut down scheduler.

cymorrow, you have my opinion and NullUnit's. The only part of NullUnit's last message with which I can agree is that I do not know Apple's actual reason for making the change to require human interaction in this instance. Just remember that NullUnit cannot know Apple's reason and its validity either.

Yes, please let me know if you get this answered as I am doing the Sam etching, wanting to shut down automatically, as iTunes needs a reboot each day, and the darn thing keeps having a stupid message about other users. Blah blah

Please get this fixed.

Matt

I have the same issue after upgrading to 10.8.

I solved it by putting this in root's crontab:

50 23 * * * halt

(shuts down 10 to midnight)

:-)

Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.

Feedback

I have been wrestling with this issue for a long time. I finally found a good posting with a number of options. Crontab as root user worked for me:

http://apple.stackexchange.com/questions/25001/how-can-i-forcibly-shut-down-my-m ac-at-an-appointed-time

I have no idea how long the above link will be active.

I have been wrestling with this issue for a long time. I finally found a good posting with a number of options. Crontab as root user worked for me:

http://apple.stackexchange.com/questions/25001/how-can-i-forcibly-shut-down-my-m ac-at-an-appointed-time

I have no idea how long the above link will be active.

I tried system preferences>energy saver>schedule shutdown but the problem is that it can be cancelled by any open application and so rarely works. I tried pmset commands in the terminal E.g. pmset repeat shutdown MTWRFSU 18:35:00 ...which did do a force shutdown but it seemed really harsh, within a second the mac and all apps shutdown, which worries me about damaging system files. I searched long and hard for a good way of doing it free from the terminal etc. In the end i experimented with 2 bought products (reluctantly, you shouldn't have to pay for this kind of app. one was powermanager by a company called dssw.co.uk, but expensive. The other one was ibeezz by a french company, which was far cheaper. Ive now been using ibeezz for a week and its excellent. Force shutdown is unstoppable but at the same time seems gentle. Unsaved work is autosaved before the shutdown and so i never lose anything and it appears the next morning saved.