Under these conditions: - SETI@Home does not have a registered user, for example if it has been updated or an account hasn't been set up through the client - SETI@Home is set to automatically start (rc-update add setiathome default) - The network connection is down, or for any reason SETI cannot phone home SETI@Home will prevent the user from loggin on. It offers two options: 1) Establish new account. 2) Log in using existing e-mail address. Both options end in a complaint that it cannot find home, and and it presents the two options again. No key combination seems to be able to kill it(CTRL-C, CTRL-C, CTRL-Break) and no other TTYs are available this early in the login process, and it appears that SSHD has not yet been started as I cannot log in remotely. Reproducible: Always Steps to Reproduce: See above Actual Results: gethostbyname: Resource temporarily unavailable Server host unknown Expected Results: If a startup program refuses to allow the system startup process to continue, there should be a way to kill it. This particular problem is is SETI@Home's fault, but Gentoo should have a way to prevent buggy programs from completely disabling a system.
I have even a worse experience with 3.08... the default config does not even try to start the client, and after I have changed the config file to point to the directory where the client really resides, I get the dialog you mentioned. After that, the client will not be started at all because the file "setiwrapper" which is referred to in the init script is not installed (seems the change to .03 didn't make it to .08). 3.08-r2 will include the wrapper and give an error message if run without login instead of trying to do so. About your problem when the network is down, I was unable to reproduce it. Could you please give more detailed instructions what you have to do in order to have it hang?
If you can provide information on how to reproduce the problem, please re-open this bug.
