Getting the webserver, remote login to START when my computer restarts....
I have a login screen where you have to enter your password before logging on.
The problem is when the power goes out and my computer boots back up, I can't access it via ssh/sftp/html.
Without having the login screen disabled, my sis-in-law lives with me and she would reek havoc on a metal block, I don't want to chance her screwing something up so how can I have my services start up and be protected immediately upon rebooting?
Make sense?
Eric
The problem is when the power goes out and my computer boots back up, I can't access it via ssh/sftp/html.
Without having the login screen disabled, my sis-in-law lives with me and she would reek havoc on a metal block, I don't want to chance her screwing something up so how can I have my services start up and be protected immediately upon rebooting?
Make sense?
Eric
Comments
Am I missing something?
I am going to give it another shot right now since I am not at home and see if I can get in. If not, I will be back and post an update.
PS once I log in to my account, everything works perfect. Go figure.
Eric
UPDATE: I can't reach my web server or use SFTP or ssh in. I called home and my computer is at the log in screen.
Update 2: I called back home and the second my wife logged on to my account my webpage came up and my sftp connection fired up perfectly.
Any thoughts?
Thanks!!
Eric
However, if I log out of my account, everything continues to work just fine even though it is at the login screen and I am totally logged out.
Am I missing a setting?
Eric
I did some looking around and it seems that the ftp and ssh files in /etc/xinetd.d/ might control ftp and ssh, I tried turning on and off ftp and ssh in System Prefs, and in each file it should say "disable = no" if a particular service is on. Maybe someone who knows more about this can elaborate if killing and restarting xinetd is a safe idea.
I appreciate your response and willingness to help me out.
Anyone ever seen this before or is this common on the Mac for the services not to start until you log in?
Maybe this needs to be moved to the genius bar?
eric
aplnub: Did you check the hostconfig file? Even if you don't feel comfortable making changes to it, still check it out and see what it says.
Update: Thanks to the terminal...
##
# /etc/hostconfig
##
# This file is maintained by the system control panels
##
# Network configuration
HOSTNAME=-AUTOMATIC-
ROUTER=-AUTOMATIC-
# Services
AFPSERVER=-YES-
AUTHSERVER=-NO-
AUTOMOUNT=-YES-
CUPS=-YES-
IPFORWARDING=-NO-
IPV6=-YES-
MAILSERVER=-YES-
NETINFOSERVER=-AUTOMATIC-
NFSLOCKS=-AUTOMATIC-
NISDOMAIN=-NO-
RPCSERVER=-AUTOMATIC-
TIMESYNC=-YES-
QTSSERVER=-NO-
WEBSERVER=-YES-
SMBSERVER=-NO-
DNSSERVER=-NO-
COREDUMPS=-NO-
VPNSERVER=-NO-
Eric
I personally overcame this by just enabling automatic login of my account. You specified you didnt want to do this... you could create a pretty restrictive user account and set it to automatic login, just for the purpose of getting ssh started. This would be a temporary solution until you can figure out if its possible to get sshd started without logging in.
Originally posted by AsLan^
I encountered the same issue the other day... I suspect it has to do with OS X not starting any particular service until a user logs in that has that service enabled.
This is probably a security feature.
When I disabled airport and connected via ethernet, set the startup option to default to a log in screen (as opposed to the auto login) and restarted the computer... I was able to ssh and vnc in to the computer (sorry I forgot to check httpd but I assume it would have worked).
Then I unplugged ethernet and reconnected with airport and reset. After it came up to the login screen I couldnt even ping it... it hadnt yet connected to the network. After logging in it immediately connected to the network and I was able to access the services.
Anyone want to guess why it won't with airport but will with a cable?
Also, yes, I have thought about making a totally restricted account to auto log in until I get this figured out. Thanks for the advice.
Thank you!!!
Update: Using the ethernet cable works at the login screen. Why won't Airport? Do you think Tiger will be any different?
Eric
If anyone else who knows a bit more about the startup process involved with OS X, I would be interested to know if we could automatically start the airport without logging in.
You see, when you log in, the computer automatically connects to the latest/preferred wireless network and fetches the password used from your keychain. Before you log in (providing a password to unlock your keychain), the keychain is locked and the wireless password can not be retrieved.
To test this, you could open up the keychain application (in the utilities folder) and change your keychain to not automatically unlock. Then when you log in, the system should ask you for a password to unlock your keychain before connecting to the network.
Similarly, other users must have the password to the wireless netword stored in their keychains as well. Try creating a new user, restarting the computer, then logging in as the new user. I suspect, there would be no network unless you punch in the password or first log in with a user that can connect.
One solution may be to store the password to the wireless network in the Network preference pane. You can choose to always join a specific network and I believe you can set the password there. Then, I would hope it would connect. However, I haven't tested this out myself.
Eric
It appears the wireless network will not start until someone logs on. Bummer.
The wire is in the computer since this feature is a must for me.
Eric