Displaying 3 results from an estimated 3 matches for "tvalp".
Did you mean:
tval
2018 Dec 03
2
Samba 4.9.3 and the "10 hour problem"
Hmm…
I see that there is a patch in the bugzilla page for that bug. I guess I could try that one… :-)
I notice in the patch that there is a lot of talk about SMB2 - we use SMB3 mostly now. But perhaps there is some code sharing? Or perhaps SMB2 is used when talking to the AD servers? Or the few SMB2-talking clients causes the problem for all of the other users? When testing the “timeout” issue I
2018 Jun 25
2
Samba 4.7.1 Generating Core Dumps
...false
mem_ctx = 0x55b48e61ca40
status = <optimized out>
seqnum = 0
async_echo = <optimized out>
from_client = <optimized out>
__FUNCTION__ = "smbd_server_connection_read_handler"
#28 0x00007fc225062f6b in epoll_event_loop (tvalp=0x7ffcba8c5e30, epoll_ev=0x55b48e627c30) at ../tevent_epoll.c:728
fde = <optimized out>
flags = <optimized out>
mpx_fde = <optimized out>
ret = 1
i = 0
timeout = <optimized out>
wait_errno = <optimized out>...
2018 Oct 05
2
Samba Panic when accessing share from OSX
...interactive at entry=false) at ../source3/smbd/process.c:4127
#23 0x000055f77e69f1d4 in smbd_accept_connection (ev=0x55f77ed45710,
fde=<optimized out>, flags=<optimized out>, private_data=<optimized
out>) at ../source3/smbd/server.c:1030
#24 0x00007f5af61eef6b in epoll_event_loop (tvalp=0x7fff8b143870,
epoll_ev=0x55f77ed463d0) at ../tevent_epoll.c:728
#25 epoll_event_loop_once (ev=<optimized out>, location=<optimized
out>) at ../tevent_epoll.c:930
#26 0x00007f5af61ed337 in std_event_loop_once (ev=0x55f77ed45710,
location=0x55f77e6a3083 "../source3/smbd/server.c:13...