From owner-freebsd-current Tue Aug 4 06:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21290 for freebsd-current-outgoing; Tue, 4 Aug 1998 06:06:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise-atm.cs.unm.edu [198.83.90.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA21232 for ; Tue, 4 Aug 1998 06:05:56 -0700 (PDT) (envelope-from cfaehl@cs.unm.edu) Received: from avarice.cs.unm.edu [198.83.92.131] by enterprise.cs.unm.edu with esmtp (Exim 1.80 #2) id 0z3gmR-0004Yd-00; Tue, 4 Aug 1998 07:05:31 -0600 X-Mailer: exmh version 2.0.2 2/24/98 To: Gerald Ehritz cc: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 /3.0-980725 completely In-reply-to: Your message of "Tue, 04 Aug 1998 13:50:16 +0200." <199808041150.NAA15805@arcturus.dbai.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 07:05:24 -0600 From: "Chris D. Faehl" Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi to all who contributed to this, > > I made a test with FreeBSD 3.0-19980725 today, and both versions of pine 3.96 and 4.02 locks up the pc! > > Here is the history: > > 1.) We used a FreeBSD 2.2 box for modem login since 2 years. In June i upgraded to 3.0 snap and everything works except pine locks up the pc. > > 2.) We allways had NFS mounted mail- and user- dirs! ( and it worked). No changes on the server (SunOS 4.1.3_U1). > > 3.) All versions of pine (2.2.6 code, 3.0 code, version 3.96, 4.0 and 4.02) kill the machine IF i write out an attachment ( may be > 100k size) to the home dir (NFS mounted), works if write it to /tmp! > > 4.) Pine works IF i only read and write mails (mail NFS mounted)! > > > Will pine ever work across NFS ? > If not we have to switch to another mail reader! > > I am asking me, why it had worked on an old FreeBSD (2.2) system. > > Any ideas? Sure. If I recall, the consensus was, "NFS client bugs in -current". So, the problem has been recognized (not sure if it's been duplicated widely, though). Likely it'll get fixed. My Really Big Idea is: FreeBSD 3.0 is in situ. You appear to be treating it like it's a production system. Perhaps you really want to be running -stable. > > Gerald > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ------------------------------------------------------------------------------- Chris Faehl | Email: cfaehl@cs.unm.edu The University of New Mexico | URL: http://www.cs.unm.edu/~cfaehl Computer Science Dept., Rm. FEC 313 | Phone: 505/277-3016 Albuquerque, NM 87131 USA | FAX: 505/277-6927 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message