> From: Corinna Vinschen
> Sent: Thursday, May 06, 2004 9:59 AM
> On May 6 01:47, Hannu E K Nevalainen wrote:
> > > >Just a wild guess, but gethostbyname() is probably not reentrant and
> > > >can't be called from threads like that.
> > >
> > > Unless HOST is a numeric IP address, gethostbyname s
On Thu, May 06, 2004 at 11:13:43AM -0500, Brian Ford wrote:
>On Thu, 6 May 2004, Jacek Trzmiel wrote:
>
>> Nevertheless ThreadingTest.cpp posted here:
>>
>> http://cygwin.com/ml/cygwin/2004-05/msg00178.html
>>
>> still sometimes fails, even with 20040504 snapshot:
>>
>> > $ g++ ThreadingTest.cpp -l
On Thu, 6 May 2004, Jacek Trzmiel wrote:
> Nevertheless ThreadingTest.cpp posted here:
>
> http://cygwin.com/ml/cygwin/2004-05/msg00178.html
>
> still sometimes fails, even with 20040504 snapshot:
>
> > $ g++ ThreadingTest.cpp -lpthread -o ThreadingTest.exe && ./ThreadingTest.exe
> > 238 [win]
On May 6 01:47, Hannu E K Nevalainen wrote:
> > >Just a wild guess, but gethostbyname() is probably not reentrant and
> > >can't be called from threads like that.
> >
> > Unless HOST is a numeric IP address, gethostbyname should be properly
> > reentrant. The only time gethostbyname is not thread
On Wed, May 05, 2004 at 07:01:01PM -0500, Brian Ford wrote:
>On Wed, 5 May 2004, Steve Thompson wrote:
>> On Wed, 5 May 2004, Christopher Faylor wrote:
>>>Unless HOST is a numeric IP address, gethostbyname should be properly
>>>reentrant. The only time gethostbyname is not thread safe is when it
>
Hi Brian,
> > > $ g++ GetHostByNameTest.cpp -lpthread -o GetHostByNameTest.exe &&
> > > ./GetHostByNameTest.exe gethostbyname: Operation not permitted
> >
> > Win2k SP4 + hotfixes.
> > Can someone reproduce it?
>
> Sure looks alot like this:
> http://www.cygwin.com/ml/cygwin/2004-04/msg00545.htm
On Wed, 5 May 2004, Brian Ford wrote:
> On Wed, 5 May 2004, Steve Thompson wrote:
>
> > On Wed, 5 May 2004, Christopher Faylor wrote:
> >
> > > Unless HOST is a numeric IP address, gethostbyname should be properly
> > > reentrant. The only time gethostbyname is not thread safe is when it is
> > >
> From: Brian Ford
> Sent: Thursday, May 06, 2004 1:55 AM
> On Thu, 6 May 2004, Jacek Trzmiel wrote:
>
> > > $ g++ GetHostByNameTest.cpp -lpthread -o GetHostByNameTest.exe &&
> > > ./GetHostByNameTest.exe gethostbyname: Operation not permitted
> >
> > Win2k SP4 + hotfixes.
> > Can someone reproduc
On Wed, 5 May 2004, Steve Thompson wrote:
> On Wed, 5 May 2004, Christopher Faylor wrote:
>
> > Unless HOST is a numeric IP address, gethostbyname should be properly
> > reentrant. The only time gethostbyname is not thread safe is when it is
> > resolving a numeric IP.
>
> I believe that gethostb
On Thu, 6 May 2004, Jacek Trzmiel wrote:
> > $ g++ GetHostByNameTest.cpp -lpthread -o GetHostByNameTest.exe &&
> > ./GetHostByNameTest.exe gethostbyname: Operation not permitted
>
> Win2k SP4 + hotfixes.
> Can someone reproduce it?
Sure looks alot like this:
http://www.cygwin.com/ml/cygwin/2004-
> From: Christopher Faylor
> Sent: Wednesday, May 05, 2004 11:04 PM
> On Wed, May 05, 2004 at 05:38:35AM -0700, Brian Dessent wrote:
> >Jacek Trzmiel wrote:
> >
> >> void test()
> >> {
> >> /* go find out about the desired host machine */
> >> struct hostent *he = gethostbyname(HOST);
> >>
On Wed, 5 May 2004, Christopher Faylor wrote:
> On Wed, May 05, 2004 at 05:38:35AM -0700, Brian Dessent wrote:
> >Jacek Trzmiel wrote:
> >
> >> void test()
> >> {
> >> /* go find out about the desired host machine */
> >> struct hostent *he = gethostbyname(HOST);
> >> if (he == 0) {
>
> >> void test()
> >> {
> >> /* go find out about the desired host machine */
> >> struct hostent *he = gethostbyname(HOST);
> >> if (he == 0) {
> >> perror("gethostbyname");
> >> exit(1);
> >> }
> >
> >Just a wild guess, but gethostbyname() is probably not reentran
Hi,
> I can't replicate your problem, but I know where it is coming from,
> basically standard windows winsock is not geared up to handle that man
> socket connections. When a socket is made and then closed the socket
> actually stays open for about 240-300 seconds depending on your
> registry se
On Wed, May 05, 2004 at 05:38:35AM -0700, Brian Dessent wrote:
>Jacek Trzmiel wrote:
>
>> void test()
>> {
>> /* go find out about the desired host machine */
>> struct hostent *he = gethostbyname(HOST);
>> if (he == 0) {
>> perror("gethostbyname");
>> exit(1);
>> }
Hi Reini,
> But we already found out that the culprit was Norton Firewall, closing
> your socket, wasn't it?
NIS is gone.
Best regards,
Jacek.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http:/
Hi Brian,
> > void test()
> > {
> > /* go find out about the desired host machine */
> > struct hostent *he = gethostbyname(HOST);
> > if (he == 0) {
> > perror("gethostbyname");
> > exit(1);
> > }
>
> Just a wild guess, but gethostbyname() is probably not reentra
Arash Partow schrieb:
I can't replicate your problem, but I know where it is coming from,
basically standard windows winsock is not geared up to handle that man
socket connections. When a socket is made and then closed the socket
actually stays open for about 240-300 seconds depending on your
regis
Jacek Trzmiel wrote:
> void test()
> {
> /* go find out about the desired host machine */
> struct hostent *he = gethostbyname(HOST);
> if (he == 0) {
> perror("gethostbyname");
> exit(1);
> }
Just a wild guess, but gethostbyname() is probably not reentrant and
can
> -Original Message-
> From: cygwin-owner On Behalf Of Arash Partow
> Sent: 05 May 2004 12:04
> I can't replicate your problem, but I know where it is coming from,
> basically standard windows winsock is not geared up to handle that man
> socket connections. When a socket is made and then
Hi,
I can't replicate your problem, but I know where it is coming from,
basically standard windows winsock is not geared up to handle that man
socket connections. When a socket is made and then closed the socket
actually stays open for about 240-300 seconds depending on your
registry settings, this
21 matches
Mail list logo
