search for: ovsik

Hi, I rebased rw-devices patch for rsync last weekend. Seems to me it works "incrementally". Attached are * six git commits, or * one complete patch on top of current development rsync branch (master branch commit 60ef39705797c9df7069297eb4ed5feab5e88f29). bobek:/data/soft/rsync/rsync# dd if=/dev/urandom of=/dev/mapper/vg-pokus1 dd: writing to `/dev/mapper/vg-pokus1': No

...). It is useful to instruct the OOM killer never to kill sshd, since almost everyone wants it to keep on running so that they have a chance of dealing with the problem remotely. Originally I implemented this in an init script, by getting sshd's pid and writing to /proc/$pid/oom_adj, but Vaclav Ovsik pointed out in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480020 that that ends up immortalising child processes too. The attached patch is based on Vaclav's, though I tidied it up and moved chunks of it into openbsd-compat/port-linux. The use of an environment variable for configuration...

Hi, I can confirm, missing dependency on pyton-xml for 'xm new...' command. lin:/etc/xen# xm new lenny1 Unexpected error: <type 'exceptions.ImportError'> Please report to xen-devel at lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.2-1/bin/xm", line 7, in <module> main.main(sys.argv) File

Hello, I faced the problem of synchronization block devices and found the patch write-devices.diff by Darryl Dixon, that went trough this mailing list http://lists.samba.org/archive/rsync/2009-October/024037.html Unfortunately the patch was one flaw for me. It doesn't improve performance of synchronization. When I tried to test it using something like: ./rsync