On Tue 11 Dec 2007, [EMAIL PROTECTED] wrote: > I have an observation and a question. > > The observation is that I'm seeing this with a symlink that points > outside of the tree being moved. That matches the area of the recent > security fix. I'm not sure if all the reports fit that description.
The point is, you're transferring symlinks, and rsync is attempting to change the modification time of those. Where they're pointing to is irrelevant for this issue. > The question concerns the remark that the bug in the original report > only arose on systems that are not "recent." I'm seeing this moving > from a 2.6.22 to a 2.6.18 system. Those both seem pretty recent. How > recent does a system need to be to avoid this trouble? 2.6.18 was released in September 2006. That's pretty old :-) The capability to set the mtime of a symlink was introduced in 2.6.22 (I believe). > At any rate, it sounds as if the bug is not serious, and that my data > have transferred intact. True. Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
