search for: l626

...igure to allow access to "export", >> but allow access to the default empty "" export. > > nbdkit ignores the export name you pass in and always has done: > > https://github.com/libguestfs/nbdkit/blob/a2c4e88af503310892ebce6da3ac478beb47888a/src/connections.c#L626 > > The -e option on the command line is only for advertizing an export > name to clients. It is otherwise unused & unenforced. Agreed - it is not necessarily a bug for the server to permit the client to connect to different name(s) than what the server was told to advertise. >...

On Sat, Aug 4, 2018 at 10:58 PM Nir Soffer <nsoffer@redhat.com> wrote: > On Sat, Aug 4, 2018 at 4:04 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > >> This is only lightly tested (against just qemu NBD client), and the >> code might be structured a little better as the >> _negotiate_handshake_newstyle_options function has now grown to be >> huge.

...;> but allow access to the default empty "" export. > > > > > > nbdkit ignores the export name you pass in and always has done: > > > > > > > > https://github.com/libguestfs/nbdkit/blob/a2c4e88af503310892ebce6da3ac478beb47888a/src/connections.c#L626 > > > > > > The -e option on the command line is only for advertizing an export > > > name to clients. It is otherwise unused & unenforced. > > > > Agreed - it is not necessarily a bug for the server to permit the client > > to connect to different...

...nteresting puzzle to crunch! Looking at these few bread-crumbs, I wager an educated guess that this loops in `sendcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 In both cases we run an infinite loop with `select()` to wait up to 1 second and `read()` from the pipe. The common expectation is that if there is nothing to read, the program bl...

...nteresting puzzle to crunch! Looking at these few bread-crumbs, I wager an educated guess that this loops in `sendcmd()` (where CLI child processes talk to a daemonized copy which tracks the timers for events), around here: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 for the daemon and here for the child: https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 In both cases we run an infinite loop with `select()` to wait up to 1 second and `read()` from the pipe. The common expectation is that if there is nothing to read, the program bl...

...have a bug - server configure to allow access to "export", > but allow access to the default empty "" export. nbdkit ignores the export name you pass in and always has done: https://github.com/libguestfs/nbdkit/blob/a2c4e88af503310892ebce6da3ac478beb47888a/src/connections.c#L626 The -e option on the command line is only for advertizing an export name to clients. It is otherwise unused & unenforced. One day we'll do something useful with it but we're not sure what. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read...

...ot;export", > >> but allow access to the default empty "" export. > > > > nbdkit ignores the export name you pass in and always has done: > > > > > https://github.com/libguestfs/nbdkit/blob/a2c4e88af503310892ebce6da3ac478beb47888a/src/connections.c#L626 > > > > The -e option on the command line is only for advertizing an export > > name to clients. It is otherwise unused & unenforced. > > Agreed - it is not necessarily a bug for the server to permit the client > to connect to different name(s) than what the server w...

...nch! > > Looking at these few bread-crumbs, I wager an educated guess that this > loops in `sendcmd()` (where CLI child processes talk to a daemonized copy > which tracks the timers for events), around here: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 > for the daemon and here for the child: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 > > In both cases we run an infinite loop with `select()` to wait up to 1 > second and `read()` from the pipe. The common expectation is that if there > is no...

...nch! > > Looking at these few bread-crumbs, I wager an educated guess that this > loops in `sendcmd()` (where CLI child processes talk to a daemonized copy > which tracks the timers for events), around here: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L583-L626 > for the daemon and here for the child: > https://github.com/networkupstools/nut/blob/v2.8.0/clients/upssched.c#L762-L787 > > In both cases we run an infinite loop with `select()` to wait up to 1 > second and `read()` from the pipe. The common expectation is that if there > is no...

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hello everyone, 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3 Binaries will be added as they become available. There are currently no open release blockers, which means if nothing new comes up, the final release could ship soon and this is