Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!pilchuck!dataio!gtenmc!fst
From: fst@gtenmc.UUCP (Fariborz "Skip" Tavakkolian)
Newsgroups: comp.sys.att
Subject: Re: problem using tar under system V
Message-ID: <368@gtenmc.UUCP>
Date: 29 Dec 89 20:19:14 GMT
References: <1295@amethyst.math.arizona.edu>
Reply-To: fst@gtenmc.UUCP (Fariborz Skip Tavakkolian)
Organization: GTE Telecom, Inc.  Bothell, WA
Lines: 26

In article <1295@amethyst.math.arizona.edu> mat@zeus.opt-sci.arizona.edu (Mat Watson) writes:
[delete]
>so we tried to use tar.  However, the tar command on his system quits
>after it has writen roughly 2Mb to the archive file ...
>Tar always quits at the same number of bytes no matter what kind of device
>or file we try to write to ( a pipe or a disk file ) ...
>Is tar under system V broken?  Any ideas on a workaround?
>Thanks in advance.
>Mat Watson
>..{allegra,cmcl2,hao!noao}!arizona!zeus.opt-sci.arizona.edu!mat

This looks like the ULIMIT problem; by default most 3B2, 6386 etc. are
setup with a ULIMIT of 2048 (1K) blocks.  There is information in the AT&T
manuals on how to change the system limits.

P.S., I am working on a VAX 8810 with 128 MB of main memory (RAM) running
SVR3.1 and close to a GAZILION MB of disk; the  ULIMIT is set to 2048, makes
no sense whatsoever ...

Skip

-- 
----------------------------------------------------------------------------
Fariborz "Skip" Tavakkolian  -of-  Automated Cellular Engineering
Currently consulting         -at-  GTE Telecom, Inc. Bothell, Wa
Mail:                              tiny1!fst@mcgp1  -or-  fst@gtenmc