similar to: GSoC 2012: Learning To Rank

Hi, When running an rsync command of the form: $ rsync -avn --delete remotehost:/mnt/volsw_dev/AS5/ /mnt/volsw_dev/AS5 rsync wants to delete a slew of files and directories. Partial output includes, for example: deleting AS5/zeromq/2.2.0/share/man/man7/zmq_tcp.7 deleting AS5/zeromq/2.2.0/share/man/man7/zmq_pgm.7 deleting AS5/zeromq/2.2.0/share/man/man7/zmq_ipc.7 deleting

Hi, As suggested earlier, I'm getting adept with the usage of ZeroMQ and understand its usage in the present context. What I have done till now is :- (1) Study ZeroMQ API and get in ease with its usage. Still implementing sample programs and learning basic functions. (2) Installed, compiled and setup my development environment with Xapian and ZeroMQ. Lots of work here already! Though, I

Hi everyone, This is Ankit; currently final-year Computer Science undergrad at Panjab University, India. I am well versed in C++ and have a pretty decent understanding of sockets. I successfully completed GSoC last year for IDI, project titled - Google App Module for ATutor. Quite recently, I have been working on the project idea - Replacing Xapian socket code with ZeroMQ. This is to inquire

On Tue, Jan 3, 2017 at 3:53 PM, Whit Armstrong <armstrong.whit at gmail.com> wrote: > > I maintian the rzmq project. > > love to get it running on windows, but zmq doesn't play nicely with R's > mingw. It's fairly easy to link against the libraries from rwinlib: https://github.com/rwinlib/zeromq. I'll send you a pull request later this week to fix the binary

Possibly so. However, the ZeroMQ libraries do exist for Windows, so it might be possible to get the package working there. However, CRAN probably won't have the libraries, so cannot produce a binary package, and it is also quite possible that the package author is not a Windows person. At the very least, you'll need some familiarity with the Windows toolchain and be prepared to apply a

Hyper-V SynIC (synthetic interrupt controller) device implementation. The implementation contains: * msr's support * irq routing setup * irq injection * irq ack callback registration * event/message pages changes tracking at Hyper-V exit * Hyper-V test device to test SynIC by kvm-unit-tests Andrey Smetanin (7): standard-headers/x86: add Hyper-V SynIC constants target-i386/kvm: Hyper-V

Hyper-V SynIC (synthetic interrupt controller) device implementation. The implementation contains: * msr's support * irq routing setup * irq injection * irq ack callback registration * event/message pages changes tracking at Hyper-V exit * Hyper-V test device to test SynIC by kvm-unit-tests Andrey Smetanin (7): standard-headers/x86: add Hyper-V SynIC constants target-i386/kvm: Hyper-V

On 10/09/2015 07:39 AM, Denis V. Lunev wrote: > From: Andrey Smetanin <asmetanin at virtuozzo.com> > > A new vcpu exit is introduced to notify the userspace of the > changes in Hyper-V synic configuraion triggered by guest writing to the s/configuraion/configuration/ Is 'synic' intended? Is it short for something (if so, spelling it out may help)? > +++

On 10/09/2015 07:39 AM, Denis V. Lunev wrote: > From: Andrey Smetanin <asmetanin at virtuozzo.com> > > A new vcpu exit is introduced to notify the userspace of the > changes in Hyper-V synic configuraion triggered by guest writing to the s/configuraion/configuration/ Is 'synic' intended? Is it short for something (if so, spelling it out may help)? > +++

This patchset implements the KVM part of the synthetic interrupt controller (SynIC) which is a building block of the Hyper-V paravirtualized device bus (vmbus). SynIC is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI

This patchset implements the KVM part of the synthetic interrupt controller (SynIC) which is a building block of the Hyper-V paravirtualized device bus (vmbus). SynIC is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI

On Sun, 2 Oct 2016 22:01:32 -0600 "Paul R. Ganci via samba" <samba at lists.samba.org> wrote: > > > On 10/02/2016 07:57 PM, Paul R. Ganci via samba wrote: > > > > > > On 10/02/2016 06:15 PM, Paul R. Ganci via samba wrote: > >> On 09/11/2016 10:38 AM, Paul R. Ganci via samba wrote: > >> > >>> On 09/11/2016 01:23 AM, Rowland

Ugh, I was upgrading the AD server running on a CentOS 6.8 which uses named as its back-end. I have been running it for years with no problems. Today after upgrading bind named will not start. I get this error: Sep 28 23:32:25 nikita named[6369]: ---------------------------------------------------- Sep 28 23:32:25 nikita named[6369]: BIND 9 is maintained by Internet Systems Consortium, Sep 28

Signed-off-by: Andrey Smetanin <asmetanin at virtuozzo.com> Reviewed-by: Roman Kagan <rkagan at virtuozzo.com> Signed-off-by: Denis V. Lunev <den at openvz.org> CC: Vitaly Kuznetsov <vkuznets at redhat.com> CC: "K. Y. Srinivasan" <kys at microsoft.com> CC: Gleb Natapov <gleb at kernel.org> CC: Paolo Bonzini <pbonzini at redhat.com> CC: Roman

Dear all R users I have been trying to plot a group of intervals by using the bottom code: > breaks <- factor(cut(col3,breaks=360+5*(0:155))) > par(tck=0,lty="solid") > plot(breaks,ann=FALSE,axes=FALSE) col3 is just a column of 1500 floating point data. Unfortunately when i do the plot, the x-axis has some of the intervals as labels dispite me having both 'ann'

From: Andrey Smetanin <asmetanin at virtuozzo.com> Hypervisor Top Level Functional Specification v3.1/4.0 notes that cpuid (0x40000003) EDX's 10th bit should be used to check that Hyper-V guest crash MSR's functionality available. This patch should fix this recognition. Currently the code checks EAX register instead of EDX. Signed-off-by: Andrey Smetanin <asmetanin at

From: Andrey Smetanin <asmetanin at virtuozzo.com> Hypervisor Top Level Functional Specification v3.1/4.0 notes that cpuid (0x40000003) EDX's 10th bit should be used to check that Hyper-V guest crash MSR's functionality available. This patch should fix this recognition. Currently the code checks EAX register instead of EDX. Signed-off-by: Andrey Smetanin <asmetanin at

Hi All, A while ago I replaced a Samba AD on old hardware with a another AD on newer hardware. Everything went smoothly including the demotion of the old AD. However after I did some cleanup DNS records and turned off the old hardware I noticed that there still was a NS record associated with the old AD. So I went to the wiki page https://wiki.samba.org/index.php/DNS_Administration and

Hyper-V SynIC is a Hyper-V synthetic interrupt controller. The test runs on every vCPU and performs the following steps: * read from all Hyper-V SynIC MSR's * setup Hyper-V SynIC evt/msg pages * setup SINT's routing * inject SINT's into destination vCPU by 'hyperv-synic-test-device' * wait for SINT's isr's completion * clear Hyper-V SynIC evt/msg pages and destroy

Hyper-V SynIC is a Hyper-V synthetic interrupt controller. The test runs on every vCPU and performs the following steps: * read from all Hyper-V SynIC MSR's * setup Hyper-V SynIC evt/msg pages * setup SINT's routing * inject SINT's into destination vCPU by 'hyperv-synic-test-device' * wait for SINT's isr's completion * clear Hyper-V SynIC evt/msg pages and destroy