Mac OS forum


autologin doesn't always work after restart?

by long_tracks / February 25, 2014 2:53 AM PST

I have several Mac OS X VMs and Mac Minis running 10.8.4. A typical VM says it has a 2.28 GHz 'Unknown' processor with 4GB DRAM. They all have a particular user which has admin rights. They're all told to restart daily (some other machine - the master - ssh's in as the same admin user and does a sudo shutdown -r now)

All machines are configured to have this particular admin user autologin and run an AppleScript 'Application' which basically runs a bash shell script which calls java with a jar and a URL for something on the master using HTTPS ... this uses a JNLP file.

One problem is that this admin user doesn't always reliably autologin. When I find a machine where this is the case, I'm usually able to ssh into it as the same user, issue a sudo shutdown -r now, wait for the machine to restart and then this user does autologin (that is, it usually works the second time around without any changes or tweaks).

How can I figure out what's going on and make it so this user reliably does the autologin after every restart?

(Other issues with these machines include [1] occasionally a socket is closed, interrupting work being orchestrated by a remote machine which ssh's in with this same admin user ... [2] occasionally the machine will get into a state where no one can ssh in... perhaps there is a memory hog process which takes up too much RAM?)

I've tried having this admin user's login item (the bash script) sleep for 6 minutes before doing the jnlp task which involves HTTPS and the master. But I think it doesn't even get as far as autologging in this admin user.

Discussion is locked
You are posting a reply to: autologin doesn't always work after restart?
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: autologin doesn't always work after restart?
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.

All Answers

Collapse -
by R. Proffitt Forum moderator / February 25, 2014 2:59 AM PST
Collapse -
About socket closures.
by R. Proffitt Forum moderator / February 25, 2014 3:11 AM PST

That's normal and why the apps our office works on never relies on a socket to always stay open or up. As we collect data we'll open a socket, do the work then close it. That way we don't run afoul of DHCP lease expiry or one of the thousand other issues.

Only your new programmers think you can open a network socket and it will stay up without trouble.

Popular Forums
Computer Newbies 10,686 discussions
Computer Help 54,365 discussions
Laptops 21,181 discussions
Networking & Wireless 16,313 discussions
Phones 17,137 discussions
Security 31,287 discussions
TVs & Home Theaters 22,101 discussions
Windows 7 8,164 discussions
Windows 10 2,657 discussions


Help, my PC with Windows 10 won't shut down properly

Since upgrading to Windows 10 my computer won't shut down properly. I use the menu button shutdown and the screen goes blank, but the system does not fully shut down. The only way to get it to shut down is to hold the physical power button down till it shuts down. Any suggestions?