similar to: [Bug 9562] New: Systemd socket activation

I've looked in a lot of places but found nothing. I'm trying to perform an rsync between 2 RH 7.2 boxes with kernel 2.4.14. My rsync version is 2.4.6 protocol version 24 Here is the command I'm passing: /usr/bin/rsync -a -vv -C --progress --delete -e ssh /tmp remote.host.com:/tmp Everytime I run this command with one of the users, I get this error: "building file list ...

https://bugzilla.mindrot.org/show_bug.cgi?id=3747 Bug ID: 3747 Summary: ssh with ldap user account slow every time, local accounts unaffected Product: Portable OpenSSH Version: 8.9p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5 Component:

On Fri, 16 Jun 2023, Ronan Pigott wrote: > This adds support for systemd socket-based activation in the ssh-agent. > When using socket activation, the -a flag value must match the socket > path provided by systemd, as a sanity check. Support for this feature is > enabled by the --with-systemd configure flag. > > --- > Something tells me upstream would not be interested in

On 6/19/23 20:20, Damien Miller wrote: > > On Fri, 16 Jun 2023, Ronan Pigott wrote: > >> This adds support for systemd socket-based activation in the ssh-agent. >> When using socket activation, the -a flag value must match the socket >> path provided by systemd, as a sanity check. Support for this feature is >> enabled by the --with-systemd configure flag.

On 3/23/23 13:09, Laszlo Ersek wrote: > V3 was here: > <http://mid.mail-archive.com/20230215141158.2426855-1-lersek at redhat.com>. Meh, *this* version is of course v4. I updated everything in my git-format-series command line, from my bash history, from the time of posting v3, *except* of course the "-v3" option... Laszlo

https://bugzilla.samba.org/show_bug.cgi?id=8416 Summary: Please include systemd service file Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: michael+samba at stapelberg.de

On Tue, Oct 01, 2019 at 08:24:33AM -0500, Eric Blake wrote: > >+#else /* !HAVE_EXECVPE */ > >+ SET_NEXT_STATE (%.DEAD) > >+ set_error (ENOTSUP, "platform does not support socket activation"); > >+ return 0; > >+#endif > > We probably ought to add a matching nbd_supports_socket_activation() > feature function. > > Or, it would be possible

On 9/26/19 11:40 AM, Richard W.M. Jones wrote: > This adds new APIs for running a local NBD server and connecting to it > using systemd socket activation (instead of stdin/stdout). > > This includes interop tests against nbdkit and qemu-nbd which I > believe are the only NBD servers supporting socket activation. (If we > find others then we can add more interop tests in

On Thu, Sep 26, 2019 at 03:56:27PM -0500, Eric Blake wrote: > >+ /* Use /tmp instead of TMPDIR because we must ensure the path is > >+ * short enough to store in the sockaddr_un. On some platforms this > >+ * may cause problems so we may need to revisit it. XXX > >+ */ > > Is the use of socketpair() any better than creating a socket under /tmp? AIUI

This adds support for systemd socket-based activation in the ssh-agent. When using socket activation, the -a flag value must match the socket path provided by systemd, as a sanity check. Support for this feature is enabled by the --with-systemd configure flag. --- Something tells me upstream would not be interested in this patch, but as it may be useful on linux, I'm submitting it here.

On 10/1/19 9:11 AM, Richard W.M. Jones wrote: > On Tue, Oct 01, 2019 at 08:24:33AM -0500, Eric Blake wrote: >>> +#else /* !HAVE_EXECVPE */ >>> + SET_NEXT_STATE (%.DEAD) >>> + set_error (ENOTSUP, "platform does not support socket activation"); >>> + return 0; >>> +#endif >> >> We probably ought to add a matching

systemd allows sockets passed through socket activation to be named with the protocol they require. We only ever pass one socket, name it. This environment variable is currently ignored by qemu-nbd and nbdkit, but might be used by qemu-storage-daemon: https://lists.nongnu.org/archive/html/qemu-devel/2023-01/msg06114.html --- generator/states-connect-socket-activation.c | 41

https://bugzilla.samba.org/show_bug.cgi?id=10037 Summary: do_mknod fails to create socket file Product: rsync Version: 3.0.9 Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: simon.klinkert at gmail.com

This adds new APIs for running a local NBD server and connecting to it using systemd socket activation (instead of stdin/stdout). This includes interop tests against nbdkit and qemu-nbd which I believe are the only NBD servers supporting socket activation. (If we find others then we can add more interop tests in future.) The upstream spec for systemd socket activation is here:

On 9/30/19 11:32 AM, Richard W.M. Jones wrote: > This adds new APIs for running a local NBD server and connecting to it > using systemd socket activation (instead of stdin/stdout). > > This includes interop tests against nbdkit and qemu-nbd which I > believe are the only NBD servers supporting socket activation. (If we > find others then we can add more interop tests in

On 1/28/23 13:47, Richard W.M. Jones wrote: > systemd allows sockets passed through socket activation to be named > with the protocol they require. We only ever pass one socket, name > it. This environment variable is currently ignored by qemu-nbd and > nbdkit, but might be used by qemu-storage-daemon: > > https://lists.nongnu.org/archive/html/qemu-devel/2023-01/msg06114.html

On Tue, Jan 31, 2023 at 01:49:53PM +0100, Laszlo Ersek wrote: > On 1/28/23 13:47, Richard W.M. Jones wrote: > > systemd allows sockets passed through socket activation to be named > > with the protocol they require. We only ever pass one socket, name > > it. This environment variable is currently ignored by qemu-nbd and > > nbdkit, but might be used by

This adds new APIs for running a local NBD server and connecting to it using systemd socket activation (instead of stdin/stdout). This includes interop tests against nbdkit and qemu-nbd which I believe are the only NBD servers supporting socket activation. (If we find others then we can add more interop tests in future.) The upstream spec for systemd socket activation is here:

This is an alternative approach to https://listman.redhat.com/archives/libguestfs/2023-January/030535.html After discussing this with Dan Berrange we came to the conclusion that you really might want to set LISTEN_FDNAMES to arbitrary short strings (or not set it). Especially when talking to qemu-storage-daemon which would allow you to use these names on the command line. Rich.

On 9/26/19 11:40 AM, Richard W.M. Jones wrote: > This adds new APIs for running a local NBD server and connecting to it > using systemd socket activation (instead of stdin/stdout). > > This includes interop tests against nbdkit and qemu-nbd which I > believe are the only NBD servers supporting socket activation. (If we > find others then we can add more interop tests in