> On Sunday 30 March 2008, Bernardo Dal Seno wrote: >> On 29/03/2008, Eike Lantzsch <[EMAIL PROTECTED]> wrote: > [snip] >> > >> > So it IS different. I deleted /tmp/ssh-pscjC23970 which is not >> created >> > when starting ssh in a text console. Now ssh works again from an xterm >> > and Konsole. >> >> /tmp/ssh-pscjC23970 is a socket file created by ssh-agent(1). It >> seems that KDE starts ssh-agent, while that doesn't happen when you >> login. Anyway, ssh look for a running ssh-agent by reading the >> variable SSH_AUTH_SOCK; this is setup by KDE when it launches >> ssh-agent, while in the console there is no such variable (or, if >> there, refers to a different instance). This explains the different >> behavior, but why ssh hangs when connecting to ssh-agent I don't know. >> >> Ciao, >> Bernardo
> > Thank you for the explanation Bernardo. The scenario happens sometimes > when we have a blackout and the UPS is run down before I can shutdown the > workstation. After restarting there remains the stale socket file and ssh > cannot read from it. For some reasons I didn't configure /tmp to be purged > during startup. The problem never shows up if /tmp is purged of course. > Mebbe I'm going to reconfigure ... > > Saludos, > Eike If this is the usual microcontroller-based UPS you also should change the shutdown timer so the system shuts down before the UPS dies. Larry > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
