Re: [systemd-devel] delayed reply to sd-bus method invocation

2017-07-03 Thread Jason Litzinger
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

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

2017-07-03 Thread Lennart Poettering
On Mon, 03.07.17 16:28, Reindl Harald ([email protected]) wrote: > > > Am 03.07.2017 um 16:20 schrieb Lennart Poettering: > > On Mon, 03.07.17 16:12, Reindl Harald ([email protected]) wrote: > > > > > Am 03.07.2017 um 15:59 schrieb Lennart Poettering: > > > > On Mon, 03.07.17 15:53, R

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

2017-07-03 Thread Lennart Poettering
On Mon, 03.07.17 16:12, Reindl Harald ([email protected]) wrote: > Am 03.07.2017 um 15:59 schrieb Lennart Poettering: > > On Mon, 03.07.17 15:53, Reindl Harald ([email protected]) wrote: > > > > > Jul 3 15:48:01 backup-arrakis systemd: named.service: Failed at step > > > NAMESPACE spawn

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

2017-07-03 Thread Reindl Harald
Am 03.07.2017 um 16:20 schrieb Lennart Poettering: On Mon, 03.07.17 16:12, Reindl Harald ([email protected]) wrote: Am 03.07.2017 um 15:59 schrieb Lennart Poettering: On Mon, 03.07.17 15:53, Reindl Harald ([email protected]) wrote: Jul 3 15:48:01 backup-arrakis systemd: named.ser

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

2017-07-03 Thread Reindl Harald
Am 03.07.2017 um 15:59 schrieb Lennart Poettering: On Mon, 03.07.17 15:53, Reindl Harald ([email protected]) wrote: Jul 3 15:48:01 backup-arrakis systemd: named.service: Failed at step NAMESPACE spawning /usr/libexec/setup-named-chroot.sh: No such file or directory by all repsect, this

Re: [systemd-devel] horrible outout - failed at step NAMESPACE spawning

2017-07-03 Thread Lennart Poettering
On Mon, 03.07.17 15:53, Reindl Harald ([email protected]) wrote: > Jul 3 15:48:01 backup-arrakis systemd: named.service: Failed at step > NAMESPACE spawning /usr/libexec/setup-named-chroot.sh: No such file or > directory > > by all repsect, this output is completly nonsense when the reason i

[systemd-devel] horrible outout - failed at step NAMESPACE spawning

2017-07-03 Thread Reindl Harald
Jul 3 15:48:01 backup-arrakis systemd: named.service: Failed at step NAMESPACE spawning /usr/libexec/setup-named-chroot.sh: No such file or directory by all repsect, this output is completly nonsense when the reason is some "InaccessibleDirectories" no longer exists and is not prefixed with a

Re: [systemd-devel] delayed reply to sd-bus method invocation

2017-07-03 Thread Umut Tezduyar Lindskog
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

Re: [systemd-devel] delayed reply to sd-bus method invocation

2017-07-03 Thread Lennart Poettering
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

Re: [systemd-devel] 回复： 回复： [systemd-de vel] systemctl can't execute stop actually,whenservice is started by other way

2017-07-03 Thread Lennart Poettering
On Thu, 29.06.17 11:51, Oliver Neukum ([email protected]) wrote: > Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald: > > > > Am 29.06.2017 um 10:05 schrieb Oliver Neukum: > > > > > > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering: > > > > > > > > Well, it's a