Re: [libvirt] Syslog "nested job is dangerous" message

2014-07-21 Thread Sam Bobroff
On 17/07/14 17:54, Ján Tomko wrote: > On 07/17/2014 08:51 AM, Jiri Denemark wrote: >> On Thu, Jul 17, 2014 at 13:29:52 +1000, Sam Bobroff wrote: >>> On 17/07/14 12:50, Eric Blake wrote: On 07/16/2014 07:52 PM, Sam Bobroff wrote: > Hello everyone, [Can you configure your mailer to

Re: [libvirt] Syslog "nested job is dangerous" message

2014-07-17 Thread Ján Tomko
On 07/17/2014 08:51 AM, Jiri Denemark wrote: > On Thu, Jul 17, 2014 at 13:29:52 +1000, Sam Bobroff wrote: >> On 17/07/14 12:50, Eric Blake wrote: >>> On 07/16/2014 07:52 PM, Sam Bobroff wrote: Hello everyone, >>> >>> [Can you configure your mailer to wrap long lines?] >> >> [No problem, done.]

Re: [libvirt] Syslog "nested job is dangerous" message

2014-07-16 Thread Jiri Denemark
On Thu, Jul 17, 2014 at 13:29:52 +1000, Sam Bobroff wrote: > On 17/07/14 12:50, Eric Blake wrote: > > On 07/16/2014 07:52 PM, Sam Bobroff wrote: > >> Hello everyone, > > > > [Can you configure your mailer to wrap long lines?] > > [No problem, done.] > > >> After performing a migration, the syslo

Re: [libvirt] Syslog "nested job is dangerous" message

2014-07-16 Thread Sam Bobroff
On 17/07/14 12:50, Eric Blake wrote: > On 07/16/2014 07:52 PM, Sam Bobroff wrote: >> Hello everyone, > > [Can you configure your mailer to wrap long lines?] [No problem, done.] >> After performing a migration, the syslog often contains several >> messages like this: >> >> "This thread seems to

Re: [libvirt] Syslog "nested job is dangerous" message

2014-07-16 Thread Eric Blake
On 07/16/2014 07:52 PM, Sam Bobroff wrote: > Hello everyone, [Can you configure your mailer to wrap long lines?] > > After performing a migration, the syslog often contains several messages like > this: > > "This thread seems to be the async job owner; entering monitor without asking > for a

[libvirt] Syslog "nested job is dangerous" message

2014-07-16 Thread Sam Bobroff
Hello everyone, After performing a migration, the syslog often contains several messages like this: "This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous" The message makes it sound as if the user has done something dangerous but, after lo