Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!news.mathworks.com!satisfied.elf.com!usenet.elf.com!lowell
From: lowell@epilogue.com (Lowell Gilbert)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: tar to remote devices
Date: 21 Feb 95 12:09:59
Organization: Epilogue Technology Corporation, Wakefield MA
Lines: 15
Message-ID: <LOWELL.95Feb21120959@quern.epilogue.com>
References: <WCP.95Feb13154951@lpds.lpds.com> <LOWELL.95Feb14103625@quern.epilogue.com>
<LOWELL.95Feb17175432@quern.epilogue.com>
<3iap9f$k14@awfulhak.demon.co.uk>
NNTP-Posting-Host: quern.epilogue.com
In-reply-to: brian@awfulhak.demon.co.uk's message of 20 Feb 1995 19:07:27 -0000
brian@awfulhak.demon.co.uk (Brian Somers) asked:
> Is it anything to do with /proc ? Tar falls over in a heap (sig 11) when
> it sees one of those nasty files that aren't really files in /proc/*
No, that's not it either. I can reproduce the behaviour trying to tar
up a single file. The target doesn't have to be a tape drive, either:
it can be a disk file, as long as it's running across the network,
through tar's builtin rsh support (even piping tar's output to an rsh
works fine: the problem is definitely in tar's BUILTIN calls to rsh).
Be well.
Lowell
--
Lowell Gilbert lowell@epilogue.com