search for: errorno

I added LOG statements to mutex.c printing the strerror from the return values.   From   ret = pthread_mutexattr_init(&ma); in line 570   I got errorno 16 --> device busy.   But due the manual of pthread_mutex_attr_init() there should only be ENOMEM and EINVAL...   Doing gdb smbd -> run Doe not reveal anything, but I never used gdb for debugging anything. I just gave it a shot...         Gesendet: Montag, 01. April 2019 um 20:50 Uhr Von: &q...

...: Re: Re: [Samba] gencache.tdb: device busy On Tue, Apr 02, 2019 at 01:24:19PM +0200, Rouven WEILER wrote: > > > I added LOG statements to mutex.c printing the strerror from the return values. >   > From >   > ret = pthread_mutexattr_init(&ma); in line 570 >   > I got errorno 16 --> device busy. >   > But due the manual of pthread_mutex_attr_init() there should only be ENOMEM and EINVAL... >   > Doing gdb smbd -> run > Doe not reveal anything, but I never used gdb for debugging anything. I just gave it a shot... Sorry, looks a little like the libc/...

Hello, on the application that I''m working on, we are using Thin. The server implements long polling and commands that alter its internal state. Connecting to the long poll is a very fast operation, while updating the state of the server is a relatively slow operation. The long poll connection is held open until there is a change to be sent to the connection. Here is my current