search for: very_large_file

...Xen 2.0.7 DomU - RHEL4 U2 - TLS is still enabled. All networking is 100Mb Full duplex, and there are no network errors on any of the domain. Using plain vanilla bridge mode networking but using a random MAC address rather than a fixed MAC. Example of the error is user@localhost > rsync -av very_large_file domu:/media/archive/ building file list ... done very_large_file Received disconnect from 10.0.0.2: 2: Corrupted MAC on input. rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Broken pipe (32) rsync: connection unexpectedly closed (121821 bytes received so far)...

Like many others, I am new to R but old to SAS. Am I correct in understanding that R processes a data frame in a sequential ly? This would imply that large input files could be read, without the need to load the entire file into memory. Related to the manner of reading a frame, I have been looking for the equivalent of SAS _n_ (I realize that I can use a variant of which to identify an index

...ly, pam, encrypted passwords, users - everything is working fine and the other direction, NT to Linux is working too! So the problem must(?) be with smbfs, I think. I've tryed with smbfs and directly with smbclient. ny:/tmp # smbclient //lambda/tmp -U plot verysecretpassword -d 3 -c "put very_large_file" added interface ip=192.1.1.110 bcast=192.1.1.255 nmask=255.255.255.0 Client started (version 2.0.7). resolve_lmhosts: Attempting lmhosts lookup for name lambda<0x20> resolve_hosts: Attempting host lookup for name lambda<0x20> Connecting to 192.1.1.4 at port 139 Domain=[BAER-NETZWE...