beamlab@hscfvax.UUCP (850103@D.McCallie) (07/21/87)
Hello - I'm trying to get uwm up and running on a Masscomp running
X 10.4. Everything goes well until I use a menu command from uwm to
create a new xterm window (using the V6.6 xterm) on the screen. Everything
works until I try to "switch user" ('su') at which point I get the "Sorry"
message before I even get prompted for the password. I cannot 'su' to any
id, not just root. The problem doesn't go away by suid'ing everything to
root. It appears that uwm forks the new shell by using the 'system' call.
I wrote a dummy program that system's a new xterm - and this works fine,
leading me to believe that the problem does not lie with 'system' or
with xterm.
Any clues ? I hope this is not a problem that has already
been hashed to death. Thanks in advance. (BTW - any other Masscomp
X's out there ? I'd love to hear from you via email ...)
David McCallie
Children's Hospital
...harvard!hscfvax!{dpm, beamlab}diamant@hpfclp.HP.COM (John Diamant) (07/23/87)
> create a new xterm window (using the V6.6 xterm) on the screen. Everything > works until I try to "switch user" ('su') at which point I get the "Sorry" > message before I even get prompted for the password. > > David McCallie > Children's Hospital > ...harvard!hscfvax!{dpm, beamlab} I don't know what uwm might be doing, but I have seen this su problem before. It occurs when another process is trying to read from your tty (pty) at the same time as the su. The su never sees any input and somehow thinks you already typed something. Look for processes that are hanging or to see if the xterm is starting up correctly. John Diamant TSBU diamant@hpfclp or hpfclp!diamant