search for: msg00007

...ystem like systemd to spawn off the things", do you mean a full OS distro container? I installed the container using "yum --installroot=/root/fedora19lxc --releasever=19 install -y openssh, bridge-utils" which is described at https://www.redhat.com/archives/libvirt-users/2013-August/msg00007.html. I don't know how to make systemd work in my current container. And I don't know how to install a full OS distro container either. Could you give me more guidance? With my warmest regards, Cheng -----Original Message----- From: Daniel P. Berrange [mailto:berrange@redhat.com] Sent:...

...just a standalone app, do we really need to worry about > memory still reachable in globals, as that's not a true leak? Well it was a tidiness issue really. The only actual error this revealed was the memory leak in the bitmap patch (https://www.redhat.com/archives/libguestfs/2018-December/msg00007.html), and a lot of false positives which I worked my way through with a list of suppressions. > > passthru ("--error-exitcode=119"); > >- passthru_format ("--suppressions=%s/valgrind-suppressions", srcdir); > >+ passthru_format ("--suppression...

On Mon, Apr 06, 2020 at 10:19:10AM +0100, Richard W.M. Jones wrote: > v1 was here: > https://www.redhat.com/archives/libguestfs/2020-April/msg00007.html > > There's a BZ for this now which I forgot to add to the commit message: > https://bugzilla.redhat.com/show_bug.cgi?id=1814611 and https://bugzilla.redhat.com/show_bug.cgi?id=1820282 > For v2: > > - Fix incorrect reference to $TMPDIR in existing manual. > >...

...consideration, and suffered the recent situation. AFAICT, there has been a forced upgrade of what was called Alioth, with service disruption, and some other matters (lists lagging, ...) On the Alioth update status, here is the thread to follow: http://lists.debian.org/debian-devel-announce/2011/05/msg00007.html Now for the root CA (ca.debian.org <http://ca.debian.org/>), I don't know the exact situation and plan for the future. I've sent a request to Alioth admins, who have changed, to get more info, and cc'ed the -upsdev for info. cheers, Arnaud -- Linux / Unix Expert R&D -...

v1 was here: https://www.redhat.com/archives/libguestfs/2020-April/msg00007.html There's a BZ for this now which I forgot to add to the commit message: https://bugzilla.redhat.com/show_bug.cgi?id=1814611 For v2: - Fix incorrect reference to $TMPDIR in existing manual. - Separate handling for small temporary files and large temporary files. Small temporary fil...

...ng NBD_CMD_FLAG_DF to NBD_CMD_READ (again, which implies the client negotiated structured replies), and not all clients support structured replies. See also my recent thread about the potential of adding ENOTSUP as a valid error, towards the end of the message: https://lists.debian.org/nbd/2019/03/msg00007.html There, I argued that since clients do not have to have a 1:1 mapping from system errno values to NBD wire error values, that any addition of a new error value over the wire should at least think about back-compat considerations, where we should consider documenting that a server SHOULD NOT se...

Dear All, I want to start my application automatically after I start the container with a virsh command " virsh -c lxc:/// start mycontainer" How can I achieve this? Thank you in advance. Cheng

On Tue, Mar 14, 2017 at 12:07 PM, Mark Kettenis <mark.kettenis at xs4all.nl> wrote: > > Date: Tue, 14 Mar 2017 11:39:22 -0700 > > From: Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> > > > > Hi all, > > > > LLVM 4.0.0 is out, and I can say that LLD/ELF is now ready for production > > use at least for x86-64 (and probably for AArch64 and

On 12/2/18 10:39 AM, Richard W.M. Jones wrote: > By default valgrind suppresses many leaks. I'm not even sure exactly > how it decides which ones to suppress, but certainly global variables > pointing to malloc’d data are suppressed, which is not useful > behaviour. Here's my understanding of why that is the default - if you assign malloc()d storage into a global, then that

On Mon, Apr 22, 2019 at 07:50:22PM -0500, Eric Blake wrote: > Previously, we were squashing EOVERFLOW into EINVAL; continue to do so > at points in the protocol where the client may not be expecting > EOVERFLOW. > > Signed-off-by: Eric Blake <eblake@redhat.com> > --- > server/protocol.c | 16 ++++++++++------ > 1 file changed, 10 insertions(+), 6 deletions(-) >