FNDELAY! FNDELAY!

Posted by Nick Cash on Tue 12 Jul 2005 08:33 PM — 6 posts, 21,405 views.

Nick Cash USA Tue 12 Jul 2005 08:33 PM #0

I was working with SWFotE 2.0 and when I booted through GDB I got spammed like crazy with the error below. I'm not even sure what it is, but I know I've never had the problem before and I don't have time to look just yet. Maybe you could help me? :P


    if ( fcntl( desc, F_SETFL, FNDELAY ) == -1 )
    {
        perror( "New_descriptor: fcntl: FNDELAY" );
        set_alarm( 0 );
        return;
    }

Thanks :P

David Haley USA Tue 12 Jul 2005 08:43 PM #1

If fcntl is returning an error there, that's telling you that you're not allowed to make the socket desc non-blocking. As to why it won't let you make it non-blocking, that's a darn good question. :-) What have you changed recently, what are you doing differently? Has your server provider changed anything?

Nick Cash USA Wed 13 Jul 2005 12:57 AM #2

Quote:
What have you changed recently,

Nothing really. I was just installing the codebase and making the needed adjustments.

Quote:
what are you doing differently?

Nothing I know of. However, I was able to connect just fine to it later. I think it might only be if I boot it via gdb.

Quote:
Has your server provider changed anything?

No.

I think booting in gdb might really be the case on this one. I was able to connect just fine. No one was trying to connect when I got the spam, unless I'm being bombarded constantly (pesky spammers).

I'll do a little testing and check back. Think gdb could be the case? I usually attach or run core files with it, not generally boot.

David Haley USA Wed 13 Jul 2005 01:03 AM #3

I'd be fairly astounded if gdb were responsible. AFAIK, the no-delay is an almost standard command in MUDs, and people boot their MUD in gdb all the time.

Nick Cash USA Thu 14 Jul 2005 08:39 PM #4

Yeah, I've booted it via GDB many times without the warning. I think perhaps my web site may be at fault, since using PHP it trys to tell if the mud is open or not via this line:


$status = fsockopen( "ew.xidus.net", 3002, $errno, $errstr, 2 );

Seems likely to me. If it doesnt stop connections I guess it doesnt really matter.

David Haley USA Thu 14 Jul 2005 09:53 PM #5

Does your website open and then immediately close the socket? It is possible - and this is just a guess - that on the MUD side, you accept the socket, which makes the PHP code close it, and then the MUD tries to set the socket option, but in the meantime the socket is no longer there because the PHP code closed it. All this happens fairly rapidly though so I'd be surprised if it actually occurred over a network. If it all happened locally, the chances would be higher, I suppose.

Or it could be a property of the socket connection opened by PHP. *shrug* :)