From owner-freebsd-stable Sun Apr 19 17:24:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20450 for freebsd-stable-outgoing; Sun, 19 Apr 1998 17:24:53 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bsampley.vip.best.com (bsampley.vip.best.com [206.184.160.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20404 for ; Mon, 20 Apr 1998 00:24:40 GMT (envelope-from bsampley@best.com) Received: from localhost (localhost.vip.best.com [127.0.0.1]) by bsampley.vip.best.com (8.8.8/8.8.7) with SMTP id RAA00942 for ; Sun, 19 Apr 1998 17:20:39 -0700 (PDT) (envelope-from bsampley@best.com) Date: Sun, 19 Apr 1998 17:20:31 -0700 (PDT) From: Burton Sampley X-Sender: bsampley@bsampley.vip.best.com Reply-To: Burton Sampley To: stable@FreeBSD.ORG Subject: Re: pine dumps core under -stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Thanks for the help. A number of people have responded to check /etc/login.conf for per user limits. Somehow I don't think that is the problem since I *can* open the same file that causes Pine to blow up in VI wihtout VI dumping core. I tried changing all values for memory in the default section to inifinity and then logging out and back in, I still get the same results. Any other suggestions I have used Pine to open larger files at work on Solaris 2.X (on Sparc 5's) without any problems. - -burton- - --------------- Burton Sampley bsampley@best.com or bsampley@haywire.csuhayward.edu PGP key available at http://www.best.com/~bsampley/pgp.html -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNTqU1nt2O8KJtMdBAQFqdAP+OSYiSBC4ia9dUePCfdUBl1bqJABMlRvK XpXGkSCsJTiFEaVt6KjIjOZ04HrnfUtkx9CKiTmCglEhHYE5TxPM8Xu/227Aj7gN fibCj41gfvT5nMvh9pM+vj4F+Yi+Kil95LKi5M8a8MzxaPGcrlI77cJ5YtLc5g8K vaQD983nNNc= =qqz/ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message