did you know: libsmbclient has glaring memory leaks and race conditions because of the way it stores runtime option overrides that persist through config reloads via a single global static pointer variable to a linked list

and some functions, like library init (which is a thing that tends to happen concurrently when programs establish multiple connections), just modify these options unconditionally as a side effect

the entire samba code base is garbage. KDE never ran into problems because it runs each connection in a separate process…

anyway it’s my birthday and lucy baked a cake for me so i’m happy 💕

@k4t3 afaik there’s a daemon in charge of managing process pools, and it launches new processes on demand. same API for all protocols so there’s no special handling of smb. if you start multipla transfers you get multiple processes, each one establishing its own connection.