similar to: [PATCH nbdkit] server: Add -D nbdkit.environ=1 to dump the environment

--- configure.ac | 24 ++++++++++++++++++++++++ plugins/sh/call.c | 4 ++++ 2 files changed, 28 insertions(+) diff --git a/configure.ac b/configure.ac index cdddae73..9b925539 100644 --- a/configure.ac +++ b/configure.ac @@ -266,6 +266,30 @@ test (int a) ] ) +dnl 'environ' is not always declared in public header files: +dnl Linux => <unistd.h> Haiku =>

These work like plugin/filter debug flags, but apply to the internals of the server. --- docs/nbdkit.pod | 7 +++++++ docs/synopsis.txt | 2 +- server/main.c | 3 +++ server/nbdkit.syms | 2 ++ 4 files changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/nbdkit.pod b/docs/nbdkit.pod index 656f330..1bacb1d 100644 --- a/docs/nbdkit.pod +++ b/docs/nbdkit.pod @@ -177,6 +177,13 @@

Apart from removing a slightly misleading comment, this small refactoring makes subsequent commits simpler but otherwise doesn't change anything. --- server/internal.h | 3 +++ server/log.c | 15 ++++++++++----- 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/server/internal.h b/server/internal.h index e5c7f514..b43798ff 100644 --- a/server/internal.h +++

As this symbol is never exported from the server, don't call it "nbdkit_vfprintf". Also move it to a new file to make forthcoming changes easier. Fixes commit 1c230358462c349533062eda9e4072054fda0e21. --- server/Makefile.am | 1 + server/internal.h | 14 +++++----- server/log.c | 24 ----------------- server/vfprintf.c | 65 ++++++++++++++++++++++++++++++++++++++++++++++

Hello Andrew, and many thanks for your fast reply! :-) Am 08.06.2017 um 11:05 schrieb Andrew Bartlett: > I think the key to avoiding the issue is that you have listed rpc > modules which are not modules. The only rpc server module is > rpc_mdssvc_module. Ah, OK, I see - so I seem to have been wrong when assuming that I could take the output of Samba 3.5.16 "smbd -b" command

Good morning! I compiled samba 4.10.8 from source in a slackware 14.2 machine and imported a samba classic domain from an ldap backend. Everything works flawlessly except for a couple of user who are getting their accounts locked out periodically. I'm trying to debug this problem so I modified the smb.conf file of the DC so that it looks like this # Global parameters [global] ??????? dns

This is the first part of a pair of patch series which aim to let us use nbdkit_parse_size (or rather, an equivalent common function) in nbdcopy, so we can write: nbdcopy --request-size=32M ... We can't do that now which was annoying me earlier in the week. This commit creates a new function called human_size_parse which is basically nbdkit_parse_size, and turns nbdkit_parse_size into a

On Tue, Jan 31, 2023 at 10:29:00AM -0600, Eric Blake wrote: > On Mon, Jan 30, 2023 at 10:55:20PM +0000, Richard W.M. Jones wrote: > > To allow us to name the socket passed down to the NBD server when > > calling nbd_connect_systemd_socket_activation(3), we need to add the > > field to the handle and add access functions. > > --- > > generator/API.ml | 49

On Wed, Jun 19, 2019 at 01:18:01PM -0500, Eric Blake wrote: > Oddly enough, I am not getting any measurable performance difference > with this patch applied and using examples/threaded-reads-and-writes > coupled with nbdkit. My explanation is that in the common case, once > a server has something to send, it is going to send the entire reply > as fast as it can, rather than sending

On Mon, Jan 30, 2023 at 10:55:20PM +0000, Richard W.M. Jones wrote: > To allow us to name the socket passed down to the NBD server when > calling nbd_connect_systemd_socket_activation(3), we need to add the > field to the handle and add access functions. > --- > generator/API.ml | 49 ++++++++++++++++++++++++++++++++++++++++++ > lib/handle.c | 56

The immediate reason for this patch is to reduce the amount of debugging in virt-v2v with using the virt-v2v -v option (because this implies running nbdkit in verbose mode too). Most of the messages are datapath ones about pread/pwrite requests, and in fact as we've added more filters on top of nbdkit these messages have got more and more verbose. However they are not particularly

I'm pasting below the output of the debug script you sent me some time ago. Other than this Samba has been compiled with standard options, just ./configure, following the wiki guide with the offered bootstrap file for ubuntu18.04. root at fileserver:~# smbd -b Paths: SBINDIR: /usr/local/samba/sbin BINDIR: /usr/local/samba/bin CONFIGFILE: /usr/local/samba/etc/smb.conf

When processing a server reply within the REPLY subgroup, we will often hit a situation where recv() requires us to block until the next NotifyRead. But since NotifyRead is the only permitted external action while in this group, we are effectively blocking CmdIssue and NotifyWrite events from happening until the server finishes the in-progress reply, even though those events have no strict

Also test that the expected environment variable is set when connecting to nbdkit. This test requires nbdkit >= 1.35.2 which added support for -D nbdkit.environ=1 to dump the environment, and will be skipped with other versions. --- .gitignore | 1 + tests/Makefile.am | 8 +++ tests/socket-activation-name.c | 99 ++++++++++++++++++++++++++++++++++ 3 files

When the user calls nbd_set_socket_activation_name before calling nbd_connect_system_socket_activation, pass the name down to the server through LISTEN_FDNAMES. This has no effect unless the new API has been called to set the socket name to a non-empty string. --- generator/states-connect-socket-activation.c | 35 +++++++++++++++----- 1 file changed, 26 insertions(+), 9 deletions(-) diff --git

3.8p1 added the following to main() in sshd.c: #ifndef HAVE_CYGWIN /* Clear environment */ environ[0] = NULL; #endif This breaks the getenv("TZ") in session.c and causes logins to occur in GMT time. It also causes any sshd syslog messages to be written in GMT time. I'm on SCO Openserver 5.0.7, but this looks like it should affect all platforms. Am I missing something? I

To allow us to name the socket passed down to the NBD server when calling nbd_connect_systemd_socket_activation(3), we need to add the field to the handle and add access functions. --- generator/API.ml | 49 ++++++++++++++++++++++++++++++++++++++++++ lib/handle.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++ lib/internal.h | 1 + 3 files changed, 106 insertions(+) diff --git

On Mon, 2017-02-13 at 05:02 -0500, Simo Sorce wrote: > On Sat, 2017-02-11 at 10:16 -0500, Jeff Layton wrote: > > On Sat, 2017-02-11 at 08:41 -0500, Jeff Layton wrote: > > > Chad reported that he was seeing a regression in cifs-utils-6.6. > > > Prior > > > to that, cifs.upcall was able to find credcaches in non-default > > > FILE: > > >

On Thu, Mar 23, 2023 at 01:10:16PM +0100, Laszlo Ersek wrote: > When the user calls nbd_set_socket_activation_name before calling > nbd_connect_system_socket_activation, pass the name down to the server > through LISTEN_FDNAMES. This has no effect unless the new API has > been called to set the socket name to a non-empty string. > >

From: "Richard W.M. Jones" <rjones at redhat.com> To allow us to name the socket passed down to the NBD server when calling nbd_connect_systemd_socket_activation(3), we need to add the field to the handle and add access functions. [Laszlo's note: originally posted by Rich at <https://listman.redhat.com/archives/libguestfs/2023-January/030557.html>. I've renamed