Hi Oliver,
On 2010-05-21 at 16:47 +0200 Oliver Freyd sent off:
This happens on a amd64 machine, running debian lenny on top of
debian etch (with xen-3.0.3).
The virtual machine that runs samba-3.5.3 runs linux kernel 2.6.18.
Linux samba-fs1a 2.6.18-6-xen-amd64 #1 SMP Fri Aug 21 16:46:08 UTC
Björn Jacke schrieb:
Hi Oliver,
On 2010-05-21 at 16:47 +0200 Oliver Freyd sent off:
This happens on a amd64 machine, running debian lenny on top of
debian etch (with xen-3.0.3).
The virtual machine that runs samba-3.5.3 runs linux kernel 2.6.18.
Linux samba-fs1a 2.6.18-6-xen-amd64 #1 SMP Fri
This happens on a amd64 machine, running debian lenny on top of
debian etch (with xen-3.0.3).
The virtual machine that runs samba-3.5.3 runs linux kernel 2.6.18.
Linux samba-fs1a 2.6.18-6-xen-amd64 #1 SMP Fri Aug 21 16:46:08 UTC 2009
x86_64 GNU/Linux
On another machine I tried debian lenny,
I'm copying a windows share onto a samba share, with robocopy to
preserve filetimes and ACL's, but I get a lot of
ERROR 50 (0x0032) Time-stamping destination file ...
It seems samba does not like to change the timestamp to the original time.
Robocopy uses the option /copyall
These lines
