From owner-freebsd-bugs  Sun Jan  7 12:50:04 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA13206
          for bugs-outgoing; Sun, 7 Jan 1996 12:50:04 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA13200
          Sun, 7 Jan 1996 12:50:02 -0800 (PST)
Resent-Date: Sun, 7 Jan 1996 12:50:02 -0800 (PST)
Resent-Message-Id: <199601072050.MAA13200@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, taob@io.org
Received: from zip.io.org (zip.io.org [198.133.36.80])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA12902
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 7 Jan 1996 12:45:54 -0800 (PST)
Received: (from root@localhost) by zip.io.org (8.6.12/8.6.12) id PAA12899; Sun, 7 Jan 1996 15:45:04 -0500
Message-Id: <199601072045.PAA12899@zip.io.org>
Date: Sun, 7 Jan 1996 15:45:04 -0500
From: Brian Tao <taob@io.org>
Reply-To: taob@io.org
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: bin/937: rcp -p fails on files with negative timestamps
Sender: owner-bugs@freebsd.org
Precedence: bulk


>Number:         937
>Category:       bin
>Synopsis:       rcp -p fails on files with negative timestamps
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jan  7 12:50:01 PST 1996
>Last-Modified:
>Originator:     Brian Tao
>Organization:
Internex Online (shell.io.org), Toronto, Ontario, Canada
>Release:        FreeBSD 2.1-STABLE i386
>Environment:

FreeBSD zip.io.org 2.1.0-RELEASE FreeBSD 2.1.0-RELEASE #0: Sat Dec 30 14:19:27 EST 1995     taob@flinch.io.org:/src/2.1.0-RELEASE/sys/compile/ZIP  i386

>Description:

    I got this error on the client side of a large rcp (about 21
megabytes in total, only got about 3 megabytes through) while
transferring a directory hierarchy from one machine to another:

cabal# rcp -pr slynx zip:/usr/local/lib
rcp: protocol error: mtime.sec not delimited
rcp: lost connection

    The file that caused this:

cabal# ls -l about_lynx-dev.html
-rw-r--r--  1 taob  wheel  2271 Jul  1  1906 about_lynx-dev.html

    rcp'ing just that file over generates the same error, but it takes
about 10 seconds for it to appear.  No disk or network activity is
done during that time.


>How-To-Repeat:

    Create a file with a modification time of before Jan 1 1970 and
rcp -p it to another machine.


>Fix:
	
    Touching the files with the negative timestamps is a workaround.
>Audit-Trail:
>Unformatted: