From owner-freebsd-current Sat Mar 4 6:37:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id C98B537B81C for ; Sat, 4 Mar 2000 06:37:40 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id QAA13380; Sat, 4 Mar 2000 16:37:30 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Sat, 4 Mar 2000 16:37:29 +0200 (EET) From: Narvi To: Christopher Masto Cc: current@FreeBSD.ORG Subject: Re: Shared memory - Was: 2 Queries In-Reply-To: <20000301145737.A22521@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Mar 2000, Christopher Masto wrote: > On Wed, Mar 01, 2000 at 11:28:13AM -0800, John Polstra wrote: > > > It takes no more than a well-designed operating system service to > > > ensure that badly written programs don't fail to release resources > > > when they crash. > > > > We didn't design that particular service. That's why it's called > > System V shared memory. > > I did mean to imply that it was poorly designed, but not that it was > designed by FreeBSD's designers. > > > Also, it's persistent for legitimate design reasons, just like files > > are. Applications need to clean up after themselves. > > You can have many more than 32 files. Files are (usually) > well-organized and have names, so you can wipe out your web browser's > cache or lock file relatively easily. Files take up a negligible > fraction of the available file space. > > SysV shared memory is limited, unnamed, unorganized, and uses up a > very scarce resource. > > > The OS has no way of knowing whether an application wants its shared > > memory segments to survive after it terminates. > > That's unfortunate. That's one of the reasons I try to stay away from > SysV IPC. I don't like to have to reboot. You don't have to reboot. Ipcrm is you friend. > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message