[Rd] Bug in socketConnection (PR#2535)
ded@novonordisk.com
ded@novonordisk.com
Fri Feb 7 15:53:05 2003
Platform: Windows
Version: 1.6.2
When first called, socketConnection gives an error. On subsequent calls it
performs correctly. Thus the first call has the effect of "priming" the
connection. Eg
> socketConnection(port=50)
Error in socketConnection(port = 50) : unable to open connection In
addition: Warning message:
localhost:50 cannot be opened
> MIM <- socketConnection(port=50)
>
The first call gives the error irrespective of which port number is
specified. The second call shown here requires, correctly, that a socket
connection using port 50 on the local host is available.
David Edwards, PhD,
Principal Statistician,
Department of Biostatistics, Novo Nordisk A/S, Bagsværd, Denmark.
DEd@novonordisk.com <mailto:DEd@novonordisk.com>
Tlf: +45 44 42 62 35. Fax: +45 44 42 14 80
[[alternate HTML version deleted]]