You have already reported this as PR#2511. Neither report is reproducible,
since we have no idea how to reproduce the socket connection you used.
Since you are the only one with the ability to reproduce this, could you
please submit the patch needed to resolve it? (It may well be a timing
issue specific to your system, and we don't have the resources to
debug unusual uses by commercial users on platforms very few of the
developers use.)
On Fri, 7 Feb 2003 ded@novonordisk.com wrote:
> 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
--
Brian D. Ripley, ripley@stats.ox.ac.uk
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595