Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!sixhub!davidsen From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr) Newsgroups: comp.unix.xenix Subject: Re: problems with ungetty Message-ID: <1557@sixhub.UUCP> Date: 19 Aug 90 21:16:08 GMT References: Reply-To: davidsen@sixhub.UUCP (bill davidsen) Organization: *IX Public Access UNIX, Schenectady NY Lines: 24 In article paterra@cs.odu.edu (Frank C. Paterra) writes: | Ok, The two lines, tty400 and tty401, are both enabled and they | re owned by uucp and in group uucp. When nobody is calling out | and I look at the permissions, theyar are both set for -rw--w--w | . When ungetty is run (by either pcomm or uucico) the line is | shown as in use. When I type ungetty at the unix prompt and | check the return code, it shows that hte line is successfully | disabled, but if I then do a ps, I see that a getty is still | running. Sounds right to me. The way it should work is that ungetty sends a signal to getty, and getty closes the tty so the next process can use it. When that process is finished it should send *another* signal to getty to tell it to terminate. Then init will restart another getty on the line, to repeat the init code. I would expect the getty to still be there, but I can't try it because every line on this system is busy. -- bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen) sysop *IX BBS and Public Access UNIX moderator of comp.binaries.ibm.pc and 80386 mailing list "Stupidity, like virtue, is its own reward" -me