On Apr 24, 2007, at 1:52 PM, James Melin wrote:
That would work, provided I could log on to the linux guest in order to change the /etc/hosts file in the first place, which I was not able to do on one of the guests because the authentication was NOT dropping through to local authentication after the timeout. I think the logon timed out before the LDAP call failed, actually. I was able to mount the root dir on a guest that did work and change it so that we had function. Trying to get away from the very real possibility of having IPL'ed sucessfully but being unable to log on because DNS and LDAP are both unavailable.
This is among the reasons that you always, *always* should have a local user that is either privileged or that can get a privileged shell when all network connections are inoperative, which means local authentication is sufficient for that user and for its privilege escalation. This becomes merely very convenient rather than utterly necessary in a virtual environment where you can attach the disks to something else (you can do this with SAN rather easily, of course; doing it by physically transplanting an internal disk is no fun at all, although I've had to do it before). Adam ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
