Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!silver!hughes From: hughes@silver.bacs.indiana.edu (larry hughes) Newsgroups: comp.protocols.tcp-ip Subject: connect(2) timeout Message-ID: <24692@iuvax.cs.indiana.edu> Date: 16 Aug 89 21:33:48 GMT Reply-To: hughes@silver.bacs.indiana.edu (larry hughes) Organization: Indiana University, Bloomington Lines: 23 Does anyone know how to modify the default time that it takes for a connect(2) to time out? I've tried setsockopt(2) without success (I think that's for reads and writes, not connect). The default time of 1:15 is too long for my application. I've even resorted to issuing a signal(3) for SIGALRM, which causes the connect to fail with errno EINTR, but it only works the first time. Does anyone know why? Thanks for any information... /=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\ || Larry J. Hughes, Senior Programmer || hughes@silver.bacs.indiana.edu || || Indiana University || hughes@iujade.bitnet || || University Computing Services || || || 750 N. State Road 46 Bypass || "The person who knows || || Bloomington, IN 47405 || everything has a lot || || (812) 855-9255 || to learn." || \=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=/