Xref: utzoo comp.unix.aix:5929 comp.windows.x:37983 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!sun-barr!ccut!wnoc-tyo-news!sranha!sran123!sran251!m-hirano From: m-hirano@sra.co.jp Newsgroups: comp.unix.aix,comp.windows.x Subject: Re: problem with xterm on RS6000NN Message-ID: Date: 26 Jun 91 13:16:40 GMT References: <1991Jun24.202647.28977@ux1.cso.uiuc.edu> Sender: news@sran251.sra.co.JP Organization: Software Research Associates, Inc., Japan Lines: 27 In-reply-to: allender@ux1.cso.uiuc.edu's message of 24 Jun 91 20:26:47 GMT In article <1991Jun24.202647.28977@ux1.cso.uiuc.edu> allender@ux1.cso.uiuc.edu (Mark Allender) writes: >>I just installed the X11R4 clients on our IBM RS/6000 machines. Everything seems >>fine except for the xterm. When logging in on console, and starting X, the xterm >>specified by my .xinitrc comes up just fine, but the terminal control seems really ^^^^^^^^^^^^^^^^ Can you do a job control ? $ rsh rs6000 "xterm -display rs6000:0.0" ('rs6000' is your hostname.) and on this xterm, $ cat ^C Can you terminate cat ? If it works, the problem is a parameter of a struct termio|termios|sgtty for ioctl(open("/dev/pts/??"...)...). If not, you have no /dev/tty as control terminal. May be setpgrp()|setsid() fail or no open("/dev/pts/??"...) after setpgrp()|setsid(). Even if it works or not, you should fix your code of main.c of xterm. In my case, I have used xterm that posted here by IBM's man(pardon me, I forget his name !). This xterm has a problem that can't get /dev/tty. I fixed it. And I have ported kterm(Kanji xterm) and posted this in fj.sources in JUNET. Thank you for reading my funny english. -- --- m-hirano@sra.co.jp Software Research Associates, Inc., Japan