From owner-freebsd-ports Tue Feb 18 01:00:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA14843 for ports-outgoing; Tue, 18 Feb 1997 01:00:10 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA14810; Tue, 18 Feb 1997 01:00:05 -0800 (PST) Date: Tue, 18 Feb 1997 01:00:05 -0800 (PST) Message-Id: <199702180900.BAA14810@freefall.freebsd.org> To: freebsd-ports Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: ports/2756: top causes segmentation fault Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR ports/2756; it has been noted by GNATS. From: j@uriah.heep.sax.de (J Wunsch) To: kmartin@infoteam.com Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/2756: top causes segmentation fault Date: Tue, 18 Feb 1997 09:42:04 +0100 As kmartin@infoteam.com wrote: > executing top without parameters causes a segmentation fault; output > to screen no longer works afterward, but other commands still > execute. top with userid specified will often work fine. Recompile top. top is very system-dependant, and since you're running a SNAP, your first aid should be recompilation. top should probably live in the base system, not in ports. I've already removed /usr/local/bin/top on my machines at work since /usr/local is shared, but top is by no means sharable at all. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)