Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.unix.questions Subject: Re: "screen" vs. "wm" Message-ID: <6398@brl-smoke.ARPA> Date: Thu, 3-Sep-87 19:22:20 EDT Article-I.D.: brl-smok.6398 Posted: Thu Sep 3 19:22:20 1987 Date-Received: Sat, 5-Sep-87 12:21:12 EDT References: <16048@teknowledge-vaxc.ARPA> <45000012@uicsrd> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 17 In article <45000012@uicsrd> kai@uicsrd.csrd.uiuc.edu writes: >Screen is also the only package that handles window logins correctly (as far >as I know). Screen creates an entry in /etc/utmp for each window. This solved >the problem all the other packages had with any program that wanted your login >id (like talk, shutdown, su). The problem is not with other utmp-manipulating software such as "wm" or "layers", but with software such as "talk" that does not follow the procedure spelled out in the programmer's manual for determining the user name. Some applications simply can't permit "talk" etc. to certain windows (e.g. those running special communication protocols to terminal-resident processes), and they therefore make sure the coresponding utmp entry is voided. This is perfectly reasonable and should not cause problems if software follows the rules. This was discussed in comp.unix.wizards something like a year ago.