From owner-freebsd-questions Sun May 21 06:58:27 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA20361 for questions-outgoing; Sun, 21 May 1995 06:58:27 -0700 Received: from zaphod (zaphod.ttu.ee [193.40.254.227]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA20354 for ; Sun, 21 May 1995 06:58:24 -0700 Received: from juku.li.ttu.ee by zaphod (5.x/SMI-SVR4) id AA22215; Sun, 21 May 1995 16:58:05 +0300 Received: by juku.li.ttu.ee (5.x/SMI-SVR4) id AA20828; Sun, 21 May 1995 16:56:28 +0300 Date: Sun, 21 May 1995 16:56:27 +0300 (EET DST) From: Tanel Kuusk To: Alex Tang Cc: Vivek Khera , freebsd-questions@FreeBSD.org Subject: Re: iScreen seg faults In-Reply-To: <199505182155.RAA24876@petrified.cic.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@FreeBSD.org Precedence: bulk On Thu, 18 May 1995, Alex Tang wrote: > I found the same problem witn 2.0R. I also found it ONLY happened when > screen was installed as setuid root. I fixed (hacked) mine by not making > /usr/loca/bin/screen not setuid root. > > It's ugly, but it works. Does anyone REALLY know what's wrong?? I guess there's something wrong with the UTMP file processing then. If screen is setuid root, it tries to remove its parent shell from utmp and write all its windows there. If screen is not setuid root, it probably can't write utmp and all utmp processing is skipped during execution. Tanel