In non-global zones I can't use mdb for the kernel, I can work with mdb only in global zone. Dtrace functionality is also limited to userland components, so I can kernel modules only inspect by Dtrace also only in the global zone, right?
I attempt to investigate a problem of communication between smbsrv kernel module and smbd running in non-global zone.
Kernel module smbsrv communicates with smbd via socket on /var/smb/lipc/smbauth. Because smbd is running in non-gloale zone this socket path is should be related to the zone filesystem.
I assume there is only one instance of smbsrv kernel module running.?
If I investigate the problem with Dtrace in the globale zone I see that it is searched for the socket path related to the globale zone, where is no smbd running. So I get errno = 2, if the socket path do not exists in the global zone or errno = 146, if the path exists but the smbd is not running.
Who do the smbsrv kernel module knows that it has to contact the smbd socket in the non-global zone?
Or is this only an observation problem because I do the Dtracing in the global zone?
Many thanks for clarification.