[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad cp -a behaviour
From: |
Andreas Schwab |
Subject: |
Re: Bad cp -a behaviour |
Date: |
Sat, 07 Aug 2004 11:32:37 +0200 |
User-agent: |
Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) |
Tim Waugh <address@hidden> writes:
> The problem seems to be that when a destination file is written it is
> done so by opening the file without removing it first. If it is a
> hardlink to a previous destination file from the same command it will
> be overwritten.
This is required by POSIX. If you don't want this use
--remove-destination.
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- Bad cp -a behaviour, Tim Waugh, 2004/08/07
- Re: Bad cp -a behaviour,
Andreas Schwab <=
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/07
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/10
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/11
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/11
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/11
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/11
- Re: Bad cp -a behaviour, Paul Eggert, 2004/08/11
- Re: Bad cp -a behaviour, Tim Waugh, 2004/08/12
- Re: Bad cp -a behaviour, Philip Rowlands, 2004/08/12