[comp.bugs.sys5] cpio handling of read errors

chris@cetia.UUCP (Chris Bertin) (09/27/88)

There is a problem in the way 'cpio' handles read errors. If it encounters
such an error, it just continues, which causes the end of the archive to be
out of sync. This can happen if a disk has a bad block, or, much more commonly
if you are cpio'ing across NFS (if you have NFS on your SYSV) and if you hit
non-readable files.
The way to handle this problem is probably to replace the 'continue' by a
'memset(..., 0, ...);', or, simply to give up.

Chris
-- 
Chris Bertin	| CETIA
		| 150, Av Marcelin Berthelot, Z.I. Toulon-Est
+33(94)212005	| 83088 Toulon Cedex, France
Ext: 239	| inria!cetia