search for: v3hfy5db

...en. > > The prob might not be the (host) name resolution of smbclient, > but on the receiving side too. Or might be something else > entirely. Here's the output of "strace --relative-timestamps -o strace.smbclient.log smbclient -NL 127.0.0.1" : https://pastebin.com/raw/v3hFY5DB

06.11.2024 08:59, Gilles via samba wrote: >>> FWIW, there's no delay after I run it once? but only for a couple of minutes. >> >> This suggests it might be a name resolution issue. > > What files could help find the source of the problem? That's a strange question. Without understanding what the actual problem is, it's hardly possible to point to the

...t not be the (host) name resolution of smbclient, >> but on the receiving side too. Or might be something else >> entirely. > > Here's the output of "strace --relative-timestamps -o strace.smbclient.log smbclient -NL 127.0.0.1" : > > https://pastebin.com/raw/v3hFY5DB So, as you can see yourself, there are 2 interesting places (adding some context): 0.000442 writev(4, [{iov_base="\0\0\0\204", iov_len=4}, {iov_base="\376SMB@\0\1\0\0\0\0\0\5\0\1\0\20\0\0\0\0\0\0\0\4\0\0\0\0\0\0\0"..., iov_len=64}, {iov_base="9\0\0\0\2\0\0\0\0\0\0\0\0\0\...