On Mon, Jul 03, 2017 at 12:31:14PM +, Umut Tezduyar Lindskog wrote:
> Hello Jason,
>
> Just wanted to remind you that clients set a timeout for the method reply.
> Don't remember off the top of my head but different implementations have
> different default timeouts. Consider this when delaying
Hello Jason,
Just wanted to remind you that clients set a timeout for the method reply.
Don't remember off the top of my head but different implementations have
different default timeouts. Consider this when delaying the reply.
Umut
On Mon, Jul 3, 2017 at 10:36 AM Lennart Poettering
wrote:
> O
On Thu, 29.06.17 21:55, Jason Litzinger ([email protected]) wrote:
> > machined has easier-to-follow uses of this, as it does some operations
> > that might take a bit longer, such as cloning or removing images.
> Thanks!
>
> Since I'll be going through this to come up with something for my
> machined has easier-to-follow uses of this, as it does some operations
> that might take a bit longer, such as cloning or removing images.
Thanks!
Since I'll be going through this to come up with something for my
own use case, it wouldn't be much to write up a self-contained example.
Is there an
On Wed, 28.06.17 20:52, Jason Litzinger ([email protected]) wrote:
> I have a daemon using the sd-bus API with a use case that I suspect
> is supported, but wanted to see if there was an example anywhere (I've
> been looking, haven't found one yet).
>
> Is there a case in the systemd codeba
I have a daemon using the sd-bus API with a use case that I suspect
is supported, but wanted to see if there was an example anywhere (I've
been looking, haven't found one yet).
Is there a case in the systemd codebase (or something else) where a
method is invoked but its handler doesn't immediately
