but the problem is, every time winbindd fails, it leaves two stale socket
files under <private dir>msg.sock and two stale lock files under msg.lock.
so with time passing, finally it consumes all the inodes in my disk (a VM)
and I can do nothing.
I know that we can config "messaging : messaging dgm cleanup interval = 1"
to clean up the message socket, but this does not work for me as in my
case, winbindd exit when the domain_list can not be inited.
the following is where the winbindd exit
Could not fetch our SID - did we join?
unable to initialize domain list
is there any easy work around or patch can fix this issue?