similar to: Blockpeek.. A little help please

Hi, I am using virStorageVolGetInfo to get the volume size virStorageVol.download to download a normal file for VDSM project. I want to add support for block devices as well, I was able to see the size via virDomainBlockInfo and download via virDomain.blockPeek which is works fine for both file and block device. 1. Can I depend on virDomainBlockInfo for non block devices? 2. Does the

Hi, I just tried x=dom.blockPeek('disk',5,0,buf,0) and it returns AtrributeError: 'module' object has no attribute 'virDomainBlockPeek' I found this bug submission from early 09: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=492683 Is that still correct are they not implemented. Or did i screw up the command? Thanks, Steve

On 12/05/2016 05:27 AM, Shahar Havivi wrote: > Ping > Sorry for the delay... Lots of investigation, patches, and other work. > On Wed, Nov 30, 2016 at 3:13 PM, Shahar Havivi <shavivi@redhat.com > <mailto:shavivi@redhat.com>> wrote: > > Hi, > > I am using virStorageVolGetInfo to get the volume size > virStorageVol.download to download a >

Another issue here in findme.c. strlcpy() is a BSD-only method and definitely not portable. Please consider other platforms when creating patches. I can provide a patch to this patch also. Thanks, Randall From: rsync <rsync-bounces at lists.samba.org> On Behalf Of Randall S. Becker via rsync Sent: January 14, 2025 6:46 PM To: 'rsync.project' <rsync.project at

Hello all, I'm going to tackle learning C this week, and start writing my first * add-on/contribution; assuming it's actually worthy of contributing once it's done.. I think I've chosen a hefty project for my first go round here... I'd like to get some feedback from everyone on a FindMe/FollowMe spec I've put together. Before you read on, let me say, I don't want

The popt changes came from upstream popt. We have Solaris and FreeBSD CI tests, along with linux, but don't have a method for testing other platforms. If you submit a PR to fix this, please consider a way we can test the fix in CI. Cheers, Tridge On Wed, 15 Jan 2025 at 14:35, <rsbecker at nexbridge.com> wrote: > Another issue here in findme.c. strlcpy() is a BSD-only method and >

Here is my fix for the situation: diff --git a/popt/findme.c b/popt/findme.c index ac4cbae..4fe8a18 100644 --- a/popt/findme.c +++ b/popt/findme.c @@ -25,12 +25,23 @@ const char * findProgramPath(const char * argv0) if (path == NULL) return NULL; bufsize = strlen(path) + 1; +#if defined __TANDEM + start = pathbuf = malloc(bufsize); +#else start = pathbuf =

I'd also note that the patches for 3.4.0 were made available to 81 different vendors via VINCE since 18th December (under embargo to give time for vendors to prepare). It is unfortunate that it didn't cover the platform you are building for. What platform is it btw? On Wed, 15 Jan 2025 at 17:57, rsync.project <rsync.project at gmail.com> wrote: > The popt changes came from

Hi list, We're trying to set up a phone number that customers can call to get a hold of anyone of a group of sysadmins (and not their voice mails!). We found the findme example ([1]) that makes the callees press 1 to accept the call. It almost works, but it doesn't work correctly when one of the callees, the sysadmins, hangs up after accepting the call. We're using this

Also, the patch I previously sent works correctly on x86, but not ia64. This problem is isolated to popt/findme From: rsync.project <rsync.project at gmail.com> Sent: January 15, 2025 2:11 PM To: rsbecker at nexbridge.com Cc: Perry Hutchison <pluto at agora.rdrop.com>; rsync at lists.samba.org Subject: Re: new release 3.4.0 - critical security release Is there a way I can get

FYI: I think this is just missing #include ?rsync.h? in popt/findme.c From: rsbecker at nexbridge.com <rsbecker at nexbridge.com> Sent: January 14, 2025 10:35 PM To: rsbecker at nexbridge.com; 'rsync.project' <rsync.project at gmail.com> Cc: rsync at lists.samba.org Subject: RE: new release 3.4.0 - critical security release Another issue here in findme.c. strlcpy() is

Boy, am I stuck... I'm officially ready to toss Asterisk out the window. I have to admit it isn't necessarily all the fault of Asterisk either. It just seems that every option I turn to suddenly ends in failure. I don't know if it's me that's bitten of more than I can chew with this project, or maybe Asterisk just isn't mature enough yet. Nothing complicated really....

Is there a way I can get access to a machine 3.4.0 is failing to build on? Maybe a VM under VirtualBox? Or some cloud service? I don't have an ia64 On Thu, 16 Jan 2025 at 01:20, <rsbecker at nexbridge.com> wrote: > On January 14, 2025 11:20 PM, Perry Hutchison wrote: > >"Randall S. Becker via rsync" <rsync at lists.samba.org> wrote: > > > >> FYI:

Ping On Wed, Nov 30, 2016 at 3:13 PM, Shahar Havivi <shavivi at redhat.com> wrote: > Hi, > > I am using virStorageVolGetInfo to get the volume size > virStorageVol.download to download a > normal file for VDSM project. > > I want to add support for block devices as well, I was able to see the size > via virDomainBlockInfo and download via virDomain.blockPeek which

I keep getting an error when I try to attach a device in the libvirt api through python The python code is: conn=libvirt.open('qemu:///system') dom = conn.lookupByName("fedoratest") if dom.info()[0]==1: dom.attachDevice('net.xml') And I keep getting: "libvirtError: XML description not well formed or invalid The xml is a simple network

I am using the Find-me/Follow-me example below with screening: http://www.voip-info.org/wiki/view/Asterisk+tips+findme Here is my actual config: [macro-screen] exten => s,1,Wait(1) exten => s,n,Background(press-1-to-be-connected-to-the-caller) exten => s,n,Set(TIMEOUT(response=5)) exten => 1,1,NoOp(Caller accepted) exten => i,1,Set(MACRO_RESULT=CONTINUE) exten =>

"Randall S. Becker via rsync" <rsync at lists.samba.org> wrote: > FYI: I think this is just missing #include "rsync.h" in popt/findme.c Structurally, this seems very odd. I thought popt was a generic argument handler, which should not need to #include details of the application that is using it.

On January 14, 2025 11:20 PM, Perry Hutchison wrote: >"Randall S. Becker via rsync" <rsync at lists.samba.org> wrote: > >> FYI: I think this is just missing #include "rsync.h" in popt/findme.c > >Structurally, this seems very odd. I thought popt was a generic argument handler, >which should not need to #include details of the application that is

Hi to all, On Solaris 9 (and below I think), Samba 3.0.1pre1's tdbbackup now needs snprintf which is not included in Solaris. The following patch on master Makefile.in (~samba/source) should ease the compilation of tdbbackup : diff -u Makefile.in.orig Makefile.in --- Makefile.in.orig Mon Oct 20 11:06:54 2003 +++ Makefile.in Mon Oct 20 11:07:09 2003 @@ -629,7 +629,7 @@

We have a number of DID's that do the standard VoIP tricks: ringing multiple locations, findme-followme etc. What is happening more and more is that customers call those DID numbers, and draw the reasonable conclusion that they are calling mobile numbers because they literally can HEAR that the called party is on a mobile. Consequently many of those customers draw the conclusion that they