Dear all This isn't really a problem - everything works, but, rather, a VERY strange (as it appears to me) behaviour. I looked through lkml's archives, asked several news-groups - no success. So, here goes: I am observing this behaviour on 2 VERY different machines, but I'll describe one of them to make it easier. Maybe it's a known feature, so, you'll tell me straight away. Shortly - when opening new remote sessions some pts's don't get allocated, although they are not currently in use by any login (`who`), and corresponding /dev/pts/x don't exist. Already know what it is? If not - I'll give a bit more detail. This machine is running 2.2.18 (another one 2.4.2). It doesn't have X installed on it (only couple X-clients, including rxvt - an xterm clone. So, - it went like this: 1) open rxvt, pts/2 appears, `who` has extra line (I didn't check, but I assume) 2) rxvt crashes, pts/2 disappears, line in who stays, pts/2 locked 3) I re-initialize /var/run/utmp, line in who goes, pts/2 still locked (present state) On another occasion pts/4 got locked in exactly the same way, but before I re-initialized utmp, one of terminals got associated with pts/4 (then who produced 2 lines with pts/4!), and, when I closed that other session with pts/4 both lines from who disappeared and pts/4 got unlocked! VERY weird, to say the least:-) On another machine pts's get locked also when ssh sessions get cut. Any ideas? Thanks Guennadi ___ Dr. Guennadi V. Liakhovetski Department of Applied Mathematics University of Sheffield, U.K. email: [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
