Re: nc -w with -z does not seems to work.

2009/1/30 jared r r spiegel j...@ice-nine.org: check the obsd manpage, it is specifically different and does not mention connects:' But nc -h gives -w secs Timeout for connects and final net reads So I guess obsd nc does not support timeouts for connect and will wait 1m15sec if

Re: nc -w with -z does not seems to work.

On Fri, Jan 30, 2009 at 01:34:51PM +0530, Rajkumar S wrote: 2009/1/30 jared r r spiegel j...@ice-nine.org: check the obsd manpage, it is specifically different and does not mention connects:' But nc -h gives -w secs Timeout for connects and final net reads yup, you're

Re: nc -w with -z does not seems to work.

On Thu, Jan 29, 2009 at 12:26:21PM +0530, Rajkumar S wrote: Help says -w is timeout for connects and final net reads, so nc should exit after 2 seconds, and it does exit when tested under linux, but not under openbsd. check the obsd manpage, it is specifically different and does not

nc -w with -z does not seems to work.

Hi, I am using Openbsd 4.4 GENERIC#1021 and nc to check if a port is open or not. The command I use is # /usr/bin/nc -z -w 2 192.168.1.10 80 The command works fine if 192.168.1.10 is up, but if ip is non existing it takes about 1m15sec to exit. # time /usr/bin/nc -v -z -w 2 192.168.3.96 80