obsd 4.6 setsockopt SO_RCVTIMEO and -pthread
Hi list, I just noticed, that setting a socket read timeout: setsockopt(client_fd, SOL_SOCKET, SO_RCVTIMEO, (void *)&tv, sizeof(struct timeval)) does not have any effect, if the program is linked with -pthread. I haven't found anything in a man page or FAQ. Is this a bug or is there an explanation for that? Many thanks - Peter
Re: obsd 4.6 setsockopt SO_RCVTIMEO and -pthread
Federico G. Schwindt wrote: > On Mon, Mar 01, 2010 at 06:40:03PM +, Federico G. Schwindt wrote: >> On Mon, Mar 01, 2010 at 07:21:06PM +0100, Peter Haag wrote: >>> Hi list, >>> I just noticed, that setting a socket read timeout: >>> >>> setsockopt(client_fd, SOL_SOCKET, SO_RCVTIMEO, (void *)&tv, sizeof(struct >>> timeval)) >>> >>> does not have any effect, if the program is linked with -pthread. >>> I haven't found anything in a man page or FAQ. Is this a bug or is there an >>> explanation >>> for that? >> i've fixed this in -current. i take you're using 4.6. if not, i need >> more details. > > i meant, 4.6 vanilla, of course. Yes - I use 4.6 vanilla. Thanks for the quick answer! - Peter > > f.-
/bsd: file: table is full
Hi list, I'm running a moderate busy OpenBSD 6.0 server for mail ( postfix, cyrus ) as well as web server ( nginx, php ) and experiance the following kernel messages: /bsd: file: table is full /bsd: process: table is full Is there an advice or rule on how the values kern.maxfiles, kern.maxproc should be set/increased in order to avoid hitting these limits, or is it simply an increase to what every value is appropriate? On the application side, I already tried to optimize some values for IMAP etc. - fstat is the tool of choice, but all tweeking seems not to fit into the default values of the kernel. Many thanks - Peter signature.asc Description: OpenPGP digital signature
