From owner-freebsd-current Sun Apr 19 07:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27306 for freebsd-current-outgoing; Sun, 19 Apr 1998 07:54:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27301 for ; Sun, 19 Apr 1998 14:54:38 GMT (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id KAA29853; Sun, 19 Apr 1998 10:54:24 -0400 (EDT) Message-ID: <19980419105423.A29843@rtfm.net> Date: Sun, 19 Apr 1998 10:54:23 -0400 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: Re: Star Office 4 (Was: Re: Problems w/ Linux EMU) Mail-Followup-To: current@FreeBSD.ORG References: <199804172257.PAA01087@dingo.cdrom.com> <19980418111526.A7246@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980418111526.A7246@keltia.freenix.fr>; from Ollivier Robert on Sat, Apr 18, 1998 at 11:15:26AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 18, 1998 at 11:15:26AM +0200, Ollivier Robert wrote: > According to Alfred Perlstein: > > after staroffice 4 has been running for a few seconds it locks up and i do > > a ipcs and see all my shared segments are used up. > > I have a script that start StarOffice4 and then clean up the shared memory > segments afterward (it is either a bug in SO4 or a bug in our shared mem > emulation). > > I've been seeing SO4 lockups regularely too. Sometimes, you start doing > something then everything is blocked because it has gone in a tight loop, > taking huge amount of CPU. Only kill is effective. > > I don't know if it is a bug in SO4 or in the emulator. This is the same thing that happens to x11amp (I know you want sound stuff to -multimedia, but this is relevant to the discussion. It doesn't hang, but it dies on a bus error; every subsequent attempt to start it results in sigsegv. The only way to fix it (that i know of) is run this: nathan:~% cat `which ipckill` #!/bin/sh ipcs | sed "s/[ ][ ]*/ /g" | cut -f 2 -d" " | sed "s/[^0-9]//g" | xargs -t -n 1 ipcrm -m (that's one line) this will run ipcrm on everything in the ipcs list (careful, now). Thanks to brightmn for the script. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #3: Tue Apr 14 21:41:01 CEST 1998 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message