[systemd-devel] Problem when m->finish_timestamp is set before running manager_loop

[cee1]

2015-05-20 1:27 GMT+08:00 Lennart Poettering <lennart at poettering.net>:
> Hmm, can you provide a backtrace of the call chain when this happens,
> please?

The call chain is:
0xb6df1acc <manager_check_finished+308>: 0xe1a07000
0xb6e9f744 <job_finish_and_invalidate+936>: 0xe3a00000
0xb6df4bb0 <transaction_activate+3540>: 0xe59a0004
0xb6ded8e8 <manager_add_job+364>: 0xe2509000
0xb6de6080 <main+8896>: 0xe3700001

Related logs:
"""
Job mnt-data.mount/stop finished, result=canceled
"""


>
> I have now commited a patch to git, that might fix the issue, but I am
> not entirely sure, given the little information I have:
>
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=aad1976ffa25fa6901f72c300b5980ada0ef44c5
>
> Would be cool if you could check if this patch already fixes the issue
> for you.

It doesn't work :-(



-- 
Regards,

- cee1