From owner-freebsd-questions  Thu Feb  6 00:03:24 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA08167
          for questions-outgoing; Thu, 6 Feb 1997 00:03:24 -0800 (PST)
Received: from narcissus.ml.org (root@brosenga.Pitzer.edu [134.173.120.201])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA08158
          for <questions@freebsd.org>; Thu, 6 Feb 1997 00:03:20 -0800 (PST)
Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id AAA09521; Thu, 6 Feb 1997 00:03:22 -0800 (PST)
Date: Thu, 6 Feb 1997 00:03:20 -0800 (PST)
From: Stranger Bone <ben@narcissus.ml.org>
To: Perry Lucas <perry@avatarweb.com>
cc: Softweyr LLC <softweyr@xmission.com>, questions@freebsd.org
Subject: Re: Pkg Add problems?
In-Reply-To: <3.0.32.19970206013234.0090f980@mail.vt.edu>
Message-ID: <Pine.BSF.3.91.970206000220.5408E-100000@narcissus.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 6 Feb 1997, Perry Lucas wrote:

> At 06:09 PM 2/5/97 -0700, you wrote:
> >> I am installing FreeBSD onto a 2.1 gig hard drive all its
> >> own.  I am running into a PKG_Add error that is preventing
> >> the addition of packages to the system.  I get a write 
> >> error, possible corruption of package message.
> 
> >Given the sizes of your filesystems above, I'd say you're probably
> >filling /var/tmp.  The next time pkg_add pukes on you, try df and see
> >which filesystem is at or above 108%.  Or try setting TMPDIR to
> >/usr/tmp, which appears to be less likely to run out of room.
> 
> This is what I get for Debug:
> 
> proc: table is full
> Debug:  Caught SIGPIPE while trying to install <insert package name> package.
> Debug:  Switching back to VTYI

Are you doing this from sysinstall?  It's famous for that.  If you are, 
try using plain vanilla pkg_add.
 
> DF Produces:
> 
> mfs_root        89%  / 
> dev/wd0a        44%  /mnt
> /mnt/dev/wd0s1f 23%  /mnt/user
> /mnt/dev/wd0s1e 0%   /mnt/var
> /dev/wcd0c      100% /cdrom
> 
> DU Produces:
> 
> A very long list that I am not going to copy :)
> 
> I don't know what it is, probably something very simple that I am failing
> to see.  I tried increasing the VAR partition size, but the error still
> came through.  Any further ideas?
> 
> --Perry Lucas
> 



 Ben

"You have your mind on computers, it seems."