Speculating that X is on the system and maybe even VNC, that would be another avenue if the onsite person were able to get that up and going. I also realize that is not very secure, but it would be another method and something that could be scripted as a backup in case sshd fails to start in the future.
Scott On Tue, 2003-01-07 at 08:01, Robert P. J. Day wrote: > On Tue, 7 Jan 2003, Javier Gostling wrote: > > > On Tue, Jan 07, 2003 at 09:49:03AM -0500, Tibbetts, Ric wrote: > > > > > Any suggestions, speculations, "WAGs" will be very greatfully accepted! > > > > Get those two fingers to "chkconfig telnet on" and "service xinetd > > reload", then you telnet to the machine, diagnose, fix and change root > > password (in case it was snooped). > > just being pedantic, but if you enable an xinetd-managed service with > chkconfig, there is no need to reload/restart xinetd -- that's done > automagically. > > rday -- Scott Croft Unix Services Micron Technology, Inc. 208.368.1586 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list