Well, the only thing I got was that there is the return code EBUSY on all
mutexes, when I run unpatched and the issue only exists on illumos not linux.
Using debuggers etc i did not succeed due to my lacking knowledge.
> Am 21.04.2019 um 14:28 schrieb Richard Lowe :
>
> You could check whether
You could check whether the mutex already looks initialized to us using a
debugger or logging statements added to the code.
If that's the case, we can think again about relaxing the check I added in
9959.
On Sun, Apr 21, 2019, 08:20 Rouven WEILER wrote:
> Any chance to get to know what happen
Any chance to get to know what happens?
> Am 21.04.2019 um 14:12 schrieb Richard Lowe :
>
> It's possible there's a bug. It's also possible you're getting really
> unlucky and the uninitialized mutex looks valid because the magic is valid.
>
>> On Sun, Apr 21, 2019, 06:10 Rouven WEILER wrote:
It's possible there's a bug. It's also possible you're getting really
unlucky and the uninitialized mutex looks valid because the magic is valid.
On Sun, Apr 21, 2019, 06:10 Rouven WEILER wrote:
> Dear all,
>
> trying to make samba work and getting rid of my error message
>
> [2019/04/01 09:51:
Dear all,
trying to make samba work and getting rid of my error message
[2019/04/01 09:51:41.112485, 0] ../../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log)
tdb(/var/samba/lock/gencache.tdb): tdb_open_ex: tdb_mutex_init failed for
/var/samba/lock/gencache.tdb: Device busy
I followed the info of You
