search for: msg00016

Some precisions: we are not alone, some projects had similar problem: http://bugs.bitlbee.org/bitlbee/ticket/785 And the problem is really coming from NSS initialization. Discussion about the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html There is a workaround to use NSS with fork but it is more setting a flag to share some resources (primarily sockets) but must (re)initialize NSS library on all children. AFAIK why we initialize NSS library before becoming user and forking is to be able to access and read certificates and key...

...searched at build time, hardcoded, and then still need to be checked at runtime? The concern that there is no way to know which tools are used is sort of moot, since the internal command API (in the library) logs program and arguments. [1] https://www.redhat.com/archives/libguestfs/2017-February/msg00016.html -- Pino Toscano

...v at gmail.com> wrote: Some precisions: > > we are not alone, some projects had similar problem: > http://bugs.bitlbee.org/bitlbee/ticket/785 > And the problem is really coming from NSS initialization. Discussion about > the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html > Wow! Congratulations on finding the source of the problem, I bet this wasn't easy! I'm glad to see that NUT isn't faulty :-) > There is a workaround to use NSS with fork but it is more setting a flag > to share some resources (primarily sockets) but must (re)initiali...

...me precisions: >> >> we are not alone, some projects had similar problem: >> http://bugs.bitlbee.org/bitlbee/ticket/785 >> And the problem is really coming from NSS initialization. Discussion >> about the issue here : >> http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html >> > > Wow! Congratulations on finding the source of the problem, I bet this > wasn't easy! > You have done the hardest job. Once you isolate the problem occurs only when running as a deamon and not in debug mode, searching for a problem is easier. Moreover we have done...

...:506: error: expected expression before '__attribute__' make[3]: *** [cpoly.o] Error 1 make[2]: *** [R] Error 2 make[1]: *** [R] Error 1 make: *** [R] Error 1 ...the one reference to a problem like this I could find via google searches is the post at http://osdir.com/ml/lang.r.mac/2006-10/msg00016.html regarding R 2.4.0, which I could not find a response to. Any help is appreciated! Thanks, Adam Kramer

In the last month - definitely after going to 5.5 - I've tried to fsck a drive (340 days, or some such, unchecked). 960G RAID 5, I *think*, possibly serial port attachment to a JetStore RAID array. Every time I try, it gets to 70.0%, and stops. As in, I left it run last night, having started it late afternoon, and around 23:00, it was still exactly there, not even .1% more. On that, I also had

This is related to this message I posted yesterday: http://www.redhat.com/archives/libguestfs/2010-January/msg00016.html fakechroot doesn't sufficiently contain dracut, which is what was very indirectly causing that problem. However we don't need to run /sbin/new-kernel-package (in the kernel %post script). It takes a long time because dracut is so slow, and it builds an initrd that we never use. So...

...ality it opens a can of worms, as it would be a generic passthrough for options, and not really easy to handle by libguestfs. For few more details, see also the following email with a possible way to implement this that I wrote some time ago: https://www.redhat.com/archives/libguestfs/2015-December/msg00016.html One additional argument not written in the email is that using a query string as-is works only when using the "direct" backend (i.e. libguestfs runs qemu directly); since we support also launching qemu using libvirt (the "libvirt" backend), this cannot work in that case....

...hardcoded, and > then still need to be checked at runtime? The concern that there is > no way to know which tools are used is sort of moot, since the internal > command API (in the library) logs program and arguments. > > [1] https://www.redhat.com/archives/libguestfs/2017-February/msg00016.html I mostly agree with all of what you say, EXCEPT that in the past we've had cases where people have installed broken binaries on /usr/local/bin and then reported bugs against libguestfs. Therefore at configure time we need to store the actual path of the binaries we want to use (and the b...

...>>> Some precisions: >>> >>> we are not alone, some projects had similar problem: http://bugs.bitlbee.org/bitlbee/ticket/785 >>> And the problem is really coming from NSS initialization. Discussion about the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html >> >> >> Wow! Congratulations on finding the source of the problem, I bet this wasn't easy! > > > You have done the hardest job. Once you isolate the problem occurs only when running as a deamon and not in debug mode, searching for a problem is easier. > Moreo...

...nk we need to discuss how this would be exposed to plugins since at the end of the day they need to implement the feature. Background reading: - preparatory patches: https://www.redhat.com/archives/libguestfs/2019-March/msg00013.html https://www.redhat.com/archives/libguestfs/2019-March/msg00016.html - NBD protocol, see in particular NBD_CMD_BLOCK_STATUS and NBD_REPLY_TYPE_BLOCK_STATUS: https://github.com/NetworkBlockDevice/nbd/blob/master/doc/proto.md I think we shouldn't modify the pread() callback. If we decide to implement Structured Replies properly at some point in t...

This series slightly improves the way qemu-ga is installed from the RHV Tools ISO, simplifying the feedback to the user. Patch #3 sort of conflicts with patch #2 of a related series by Tomáš Golembiovský: https://www.redhat.com/archives/libguestfs/2019-February/msg00016.html Pino Toscano (3): v2v: linux: add helper functions for pkg arch and extension v2v: try to pick the right arch for qemu-ga pkgs v2v: change the reporting of RHV Tools messages/warnings/error v2v/linux.ml | 21 +++++++++++++++++++++ v2v/linux.mli | 8 ++++++++ v2v/wind...

Fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1409024

Hello all, With a really fast lookup, I think it is probably a problem of NSS initialization (key loading...) . As the problem occurs only when upsd is forked and as nss is initialized ( https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1008)before upsd deamonify ( https://github.com/networkupstools/nut/blob/master/server/upsd.c#L1035), I suspect NSS to not be fork-safe. I will

...s, hope this is a > good place to send them: Thanks a lot, I'll fix them in my next posting. Note that I recently sent v0.10 to virtio-comment, to request inclusion into the standard [1] but your comments still apply to v0.10. [1] https://lists.oasis-open.org/archives/virtio-comment/201901/msg00016.html > 1. In section 2.6.2, one reads > > If the VIRTIO_IOMMU_F_INPUT_RANGE feature is offered and the range > described by fields virt_start and virt_end doesn?t fit in the range > described by input_range, the device MAY set status to VIRTIO_- > IOMMU_S_RANGE a...

On Mar 12, 2015, at 11:55 PM, Melkor Lord <melkor.lord at gmail.com> wrote: > > On Mon, Mar 2, 2015 at 2:39 AM, Charles Lepple <clepple at gmail.com> wrote: > > > I thought start-stop-daemon was involved because it closes stdin/stdout file > > descriptors after exec()'ing the daemon. I tried "--no-close" option to no > > avail. After that, I

...then still need to be checked at runtime? The concern that there is > > no way to know which tools are used is sort of moot, since the internal > > command API (in the library) logs program and arguments. > > > > [1] https://www.redhat.com/archives/libguestfs/2017-February/msg00016.html > > I mostly agree with all of what you say, EXCEPT that in the past we've > had cases where people have installed broken binaries on > /usr/local/bin and then reported bugs against libguestfs. I would consider this situation broken anyway, and as mentioned above it will be s...

...bly have to spend more time on this over the weekend and reply with more details or ideas later. > > Background reading: > - preparatory patches: > https://www.redhat.com/archives/libguestfs/2019-March/msg00013.html > https://www.redhat.com/archives/libguestfs/2019-March/msg00016.html > - NBD protocol, see in particular NBD_CMD_BLOCK_STATUS and > NBD_REPLY_TYPE_BLOCK_STATUS: > https://github.com/NetworkBlockDevice/nbd/blob/master/doc/proto.md > > I think we shouldn't modify the pread() callback. If we decide to > implement Structured Repli...

Hello Jean-Philippe, Jean-Philippe Brucker <jean-philippe.brucker at arm.com> writes: > Makes sense, though I think other virtio devices have been developed a > little more organically: device and driver code got upstreamed first, > and then the specification describing their interface got merged into > the standard. For example I believe that code for crypto, input and GPU >

Hello Jean-Philippe, Jean-Philippe Brucker <jean-philippe.brucker at arm.com> writes: > Makes sense, though I think other virtio devices have been developed a > little more organically: device and driver code got upstreamed first, > and then the specification describing their interface got merged into > the standard. For example I believe that code for crypto, input and GPU >