From owner-freebsd-current Fri Jul 24 00:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06854 for freebsd-current-outgoing; Fri, 24 Jul 1998 00:34:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06842 for ; Fri, 24 Jul 1998 00:34:13 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id JAA05360 for ; Fri, 24 Jul 1998 09:33:48 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id JAA08600 for freebsd-current@freebsd.org; Fri, 24 Jul 1998 09:33:49 +0200 (MET DST) Date: Fri, 24 Jul 1998 09:33:49 +0200 (MET DST) Message-Id: <199807240733.JAA08600@arcturus.dbai.tuwien.ac.at> To: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > We use a 3.0-980621 and discovered soem days ago, that writing out an >attachment ( > 100k) to a file locks up the machine completely. No login >possible and also no log to screen or file. I did a new test with pine 3.96. I wrote the attachment to /tmp and it worked. So it looks like NFS is involved, but reading and writing mail across a NFS mounted dir works! Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message