similar to: openssh transport layer

Hello, glusterd has option transport.socket.bind-address that enables binding gluster to an exact IP address. This feature is necessary for HA cluster deployment. In the initial setup everything seemed fine, but after a little bit of testing I found several issues. Here are the issues I found: - NFS and selfheal daemons are started by glusterd but with volserver hard-coded to

On 06/22/2013 06:51 AM, Peter Maydell wrote: > On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: >> You were proposing to use a valid/existing MagicValue/Version/VendorID with a >> special DeviceID that does nothing. I'm saying why not use a valid/existing >> MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0,

Hi, This is perhaps a stupid question. I apologize in advance if it's already been covered, but I'm stumped... I'm using rsync to backup some file systems to a remote host. The transport is openssh-2.9.9p2. The problem does not occur when the transport is rsh. I'm invoking rsync as follows: rsync -RlHptgoD --numeric-ids -e "ssh" -rzx --stats .

This is the first step towards separating the APIs from the means by which they are carried between the remote and local system. Added a few new classes and types: * HostTransport - defines a type for talking to the Host * Host - the public contract for the host APIs * HostAgent - the QMF transport layer Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- .gitignore

On Thu, Aug 03, 2023 at 06:58:24PM +0000, Bobby Eshleman wrote: >On Thu, Aug 03, 2023 at 02:42:26PM +0200, Stefano Garzarella wrote: >> On Thu, Aug 03, 2023 at 12:53:22AM +0000, Bobby Eshleman wrote: >> > On Wed, Aug 02, 2023 at 10:24:44PM +0000, Bobby Eshleman wrote: >> > > On Sun, Jul 23, 2023 at 12:53:15AM +0300, Arseniy Krasnov wrote: >> > > >

Hi all, For anyone that's interested in setting up TLS with libvirt, but hasn't gotten around to it yet, there's a decent guide on the wiki now: http://wiki.libvirt.org/page/TLSSetup It's user focused (ie SysAdmin's), and has lots of pics explaining concepts, plus shows what needs to be done, and shows how to do it. Please note, it doesn't cover SASL, it's just

On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: > You were proposing to use a valid/existing MagicValue/Version/VendorID with a > special DeviceID that does nothing. I'm saying why not use a valid/existing > MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0, > that does nothing? Ah, I see. Well, it sounds from your

On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote: > You were proposing to use a valid/existing MagicValue/Version/VendorID with a > special DeviceID that does nothing. I'm saying why not use a valid/existing > MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0, > that does nothing? Ah, I see. Well, it sounds from your

On 2019/9/10 ??9:52, Michael S. Tsirkin wrote: > On Tue, Sep 10, 2019 at 09:13:02PM +0800, Jason Wang wrote: >> On 2019/9/10 ??6:01, Michael S. Tsirkin wrote: >>>> +#ifndef _LINUX_VIRTIO_MDEV_H >>>> +#define _LINUX_VIRTIO_MDEV_H >>>> + >>>> +#include <linux/interrupt.h> >>>> +#include <linux/vringh.h> >>>>

Hi, Thank you for the great OpenSSH package. I obtained 1.2.2 and tried it on linux 2.2.14. I had reported earlier that I saw "Transport endpoint is not connected" warning messages were observed on the linux 2.2.14 kernel with earlier release of openssh. The same happens when I used the port-forwarded HTTP connection. But this time, after accessing such http connections, I noticed

Hi, For backing chain that all images are iscsi network disk type , such as iscsi://ip/iqn../0(base image) <-iscsi://ip/iqn../1(active image). Currently, 'qemu-img info --backing-chain' command can display correct backing file info, but after starting guest with the active image in backing chain, it don't include the related <backingStore> element in dumpxml. So,

Hi Gang I gave up on running asterisk with two interfaces without it mixing up the ip addresses. So I have removed one transport definition from pjsip.conf Now * keeps complaining: res_pjsip.c:3461 ast_sip_set_tpselector_from_transport_name: Unable to retrieve PJSIP transport 'transport-name' I did a grep on /etc/asterisk for that transport name. It's in any file anymore.

This patch adds 'module' member in the 'struct vsock_transport' in order to get/put the transport module. This prevents the module unloading while sockets are assigned to it. We increase the module refcnt when a socket is assigned to a transport, and we decrease the module refcnt when the socket is destructed. Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com>

Hi, I am testing geo-replication 3.5.2 by following the instruction from https://github.com/gluster/glusterfs/blob/master/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md All commands are executed successfully without returning any error, but no replication is done from master to the slave. Enclosed please find the logs when starting the geo-replication volume. At the end of the log,

This patch adds 'module' member in the 'struct vsock_transport' in order to get/put the transport module. This prevents the module unloading while sockets are assigned to it. We increase the module refcnt when a socket is assigned to a transport, and we decrease the module refcnt when the socket is destructed. Signed-off-by: Stefano Garzarella <sgarzare at redhat.com> ---

Is it possible to use serveral protocols for a single transport section in pjsip.con? In sip.conf you could use transport=udp,ws,wss so you cound use webrtc along with your phones but if I try: [transport-udp] type=transport protocol=udp,ws,wss bind=0.0.0.0 I get an error that transport-udp is not found. Do I need a dedicated interface for WebRTC? [Feb 15 12:42:10] ERROR[3308]:

On Thu, Nov 21, 2019 at 02:45:32PM +0000, Jorgen Hansen wrote: > > From: Stefano Garzarella [mailto:sgarzare at redhat.com] > > Sent: Tuesday, November 19, 2019 12:01 PM > > This series introduces a new transport (vsock_loopback) to handle > > local communication. > > This could be useful to test vsock core itself and to allow developers > > to test their

Right now the core vsock module is the owner of the proto family. This means there's nothing preventing the transport module from unloading if there are open sockets, which results in a panic. Fix that by allowing the transport to be the owner, which will refcount it properly. Includes version bump to 1.0.1.0-k Passes checkpatch this time, I swear... Cc: stable at vger.kernel.org Acked-by:

Right now the core vsock module is the owner of the proto family. This means there's nothing preventing the transport module from unloading if there are open sockets, which results in a panic. Fix that by allowing the transport to be the owner, which will refcount it properly. Includes version bump to 1.0.1.0-k Passes checkpatch this time, I swear... Cc: stable at vger.kernel.org Acked-by:

Hi, I had previously noticed some peculiar log entries of the form error: error: channel 0: internal error: we do not read, but chan_read_failed for istate 8 in my logs. They were harmless as far as I was concerned. I checked the list archives, where the same logs have been reported and no solution was presented. Recently I tried to use rsync over ssh for backup purposes. The remote end