similar to: How do fix a good solution against spam..

Hi all, I have a data.frame with the following colnames pattern: x1 y11 x2 y21 y22 y23 x3 y31 y32 ... I.e. I have an x followed by a few y's. What I would like to do is turn this wide format into a tall format with two columns: "x", "y". The structure is that xi needs to be associated with yij (e.g. x1 should next to y11 and y12, x2 should be next to y21, y22, and

On Sat, Jan 7, 2017 at 2:30 PM, Peter Moody <mindrot at hda3.com> wrote: > so I spent a bit of time looking at this and it seems like the only > way to go, at least if I want to keep it in ssh_connect_direct(), is > to use pthreads. further, it seems like getting that accepted is > something of a long shot: Sorry, pthreads is a non-starter. I would have thought that using

As the subject says, support socket activation in virt-p2v. I have added upstream support for socket activation to nbdkit already: https://github.com/libguestfs/nbdkit/commit/7ff39d028c6359f5c0925ed2cf4a2c4c751af2e4 I posted a patch for qemu-nbd, still waiting on more reviews for that one: https://www.mail-archive.com/qemu-devel@nongnu.org/msg427246.html I tested this against old and new qemu

Dear R-developers, I would like to suggest a 'method' slot for format.ftable() (see an adjusted 'format.ftable()' below, taken from the source of R-2.15.2). At the moment, format.ftable() contains several empty cells due to the way the row and column labels are printed. This creates problems (= unwanted empty columns/rows) when converting an ftable to a LaTeX table; see an

Changes since v1: - Set probing source port to be nbd_local_port+1 instead of always using 50124 to deal with multi-disk scenario. - Set SO_REUSEADDR on client socket to avoid issues with old connections in TIME_WAIT. I've been running this for a few hours now using the updated multi-disk test and haven't seen any problems.

Here is a version of this widely used patch specific for OpenSSH 3.1p1, as it is still not in the main tree (perhap one day...) The patch avoids spending too much time when doing an ssh()/scp() on a down host, as it does not depend off the default TCP timeout used by connect(). Patch was tested on Linux, Solaris and HP-UX. The patch can also be found on:

Hi, this patch series fixes few more issues discovered by Coverity. Thanks, Pino Toscano (6): tail: check the return value pf guestfs_set_pgroup daemon: btrfs: check end_stringsbuf return values everywhere java: use cleanup handlers for structs (lists) as return values lib: qemu: improve handling of FILE* p2v: check more return values p2v: fix possible close(-1) issue cat/tail.c

The attached patch adds a new 'ConnectTimeout' option (man page updated in patch) to avoid wasting time when the target host is down. I needed that because I was using rsync/rdist over ssh for massive files update and the default connect() took too long for my purpose. The patch was tested on Linux only, but I used a similar one for ssh 1.2.XX on Linux, Solaris and HP-UX without

Hi guys. I installed dovecot 1.0.3 with sieve plugin. It looks like sieve is loaded fine by dovecot [1]. I set up dovecot to use sieve globally: protocol lda { mail_plugins = cmusieve quota sieve_global_dir = /usr/local/etc/sieve/Junk ..... } And created a sieve file which is supposed to move all the Spam marked by dspam to users's Junk folder (listed as Junk in the subscriptions

Hi, I'm trying to write my own remote shell program, It simply connects to a remote server then copy the sock fd to stdin, stdout and stderr. And it works. But I found several problems: 1. It doesn't handle characters like ^A ^E or tab (any bash/readline stuff) -> openssh itself doesn't seem to incorporate readline, so the magic is not on readline 2. If I run

Hi I''ve migrated from Passenger to Unicorn about a week ago. It''s great. Great transparency and management, thanks for this great software! A few of my Rails applications start background jobs using Kernel#fork. Of course, the ActiveRecord connections are closed and reopened again in the parent and child processes. The child process also does its job. Unfortunately, it seems

qemu-nbd is a fine NBD server. However it's not easy to compile a reliably working version on RHEL 5. This patch series allows nbdkit to be used as an alternative (qemu-nbd is still the default). Rich.

On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > > On 2018/11/30 ??8:55, Jason Wang wrote: > > > > On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > > > > > ?? If you want to compare it with > > > > > something that would be TCP or QUIC.? The fundamental > > > > > difference between > > > > > virtio-vsock

On Fri, Nov 30, 2018 at 09:10:03PM +0800, Jason Wang wrote: > > On 2018/11/30 ??8:55, Jason Wang wrote: > > > > On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: > > > > > ?? If you want to compare it with > > > > > something that would be TCP or QUIC.? The fundamental > > > > > difference between > > > > > virtio-vsock

--- p2v/conversion.c | 32 ++++++++++++++++++++++++++------ 1 file changed, 26 insertions(+), 6 deletions(-) diff --git a/p2v/conversion.c b/p2v/conversion.c index 4ff7ecc..5c0c78e 100644 --- a/p2v/conversion.c +++ b/p2v/conversion.c @@ -44,6 +44,16 @@ /* How long to wait for qemu-nbd to start (seconds). */ #define WAIT_QEMU_NBD_TIMEOUT 10 +/* Source port for probing qemu-nbd. Should be one

>Fromthe config.log file created by ./configure configure:3326: checking for sys/types.h configure:3339: gcc -c -g -O2 conftest.c >&5 configure:3342: $? = 0 configure:3345: test -s conftest.o configure:3348: $? = 0 configure:3358: result: yes configure:3627: checking sys/socket.h usability configure:3636: gcc -c -g -O2 conftest.c >&5 configure:3639: $? = 0 configure:3642: test

On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: >>> If you want to compare it with >>> something that would be TCP or QUIC. The fundamental difference between >>> virtio-vsock and e.g. TCP is that TCP operates in a packet loss environment. >>> So they are using timers for reliability, and receiver is always free to >>> discard any unacked data.

On 2018/11/30 ??8:52, Michael S. Tsirkin wrote: >>> If you want to compare it with >>> something that would be TCP or QUIC. The fundamental difference between >>> virtio-vsock and e.g. TCP is that TCP operates in a packet loss environment. >>> So they are using timers for reliability, and receiver is always free to >>> discard any unacked data.

Hello, How can I configure dovecot in order to allow subfolders on IMAP directories ? I dont find in the dovecot.conf file Thanks Sophie

Do I need to use winbind between pdc and bdc if I'm using LDAP backend? I have a PDC setup with LDAP master on backend and a BDC with slave LDAP in another building.I'm just having a problem with getting users to authenticate and use the BDC for home directories and exactly how to have W2k clients join the domain.. The BDC is in another building (connected by a slow connection) so it needs