• socket.recvline() and file_utime()

    From MCMLXXIX@VERT/MDJ to Digital Man on Thu Mar 11 21:22:08 2010
    file_touch("test.txt");
    log("original mod_time: " + file_date("test.txt"));
    log("changing file mod_time to 1267455497"); file_utime("test.txt",1267455497,1267455497);
    log("new file mod_time: " + file_date("test.txt"));
    file_remove("test.txt");

    OUTPUT:

    3/11 01:10:51p Node 1 original mod_time: 1268331052
    3/11 01:10:51p Node 1 changing file mod_time to 1267455497
    3/11 01:10:51p Node 1 new file mod_time: 1267455498

    It's driving me insane.. doesn't make sense ----------------------------------------------------

    var sock=new Socket();
    sock.bind(10088);
    sock.connect("localhost",25);
    log(time());
    log("connected: " + sock.is_connected);
    log("nonblocking: " + sock.nonblocking);

    OUTPUT:

    3/11 01:19:09p Node 2 1268331549
    3/11 01:19:09p Node 2 connected: true
    3/11 01:19:09p Node 2 nonblocking: false
    3/11 01:19:10p Node 2 null
    3/11 01:19:10p Node 2 1268331550

    -------------------------
    also driving me insane..

    does anyone have an insight on these things?

    unless I'm missing something, the sock.recvline() should wait 10 seconds
    before moving on, but it doesnt.

    ---
    þ Synchronet þ The BRoKEN BuBBLE (MDJ.ATH.CX)
  • From Digital Man@VERT to MCMLXXIX on Thu Mar 11 23:12:08 2010
    Re: socket.recvline() and file_utime()
    By: MCMLXXIX to Digital Man on Thu Mar 11 2010 01:22 pm

    file_touch("test.txt");
    log("original mod_time: " + file_date("test.txt"));
    log("changing file mod_time to 1267455497"); file_utime("test.txt",1267455497,1267455497);
    log("new file mod_time: " + file_date("test.txt"));
    file_remove("test.txt");

    OUTPUT:

    3/11 01:10:51p Node 1 original mod_time: 1268331052
    3/11 01:10:51p Node 1 changing file mod_time to 1267455497
    3/11 01:10:51p Node 1 new file mod_time: 1267455498

    It's driving me insane.. doesn't make sense

    What filesystem is "test.txt" being stored on? Some filesystems (e.g. FAT, FAT32) only support 2-second granularity for file date/times.

    Here's a Microsoft article on the subject:

    http://msdn.microsoft.com/en-us/library/ms724290%28VS.85%29.aspx


    ----------------------------------------------------

    var sock=new Socket();
    sock.bind(10088);

    Don't bind specific port numbers for outbound connections (as we discussed).

    sock.connect("localhost",25);
    log(time());
    log("connected: " + sock.is_connected);
    log("nonblocking: " + sock.nonblocking);

    OUTPUT:

    3/11 01:19:09p Node 2 1268331549
    3/11 01:19:09p Node 2 connected: true
    3/11 01:19:09p Node 2 nonblocking: false
    3/11 01:19:10p Node 2 null
    3/11 01:19:10p Node 2 1268331550

    -------------------------
    also driving me insane..

    does anyone have an insight on these things?

    unless I'm missing something, the sock.recvline() should wait 10 seconds before moving on, but it doesnt.

    I guess you didn't paste all your code - there was no call to recvline() there.

    digital man

    Snapple "Real Fact" #18:
    A jellyfish is 95% water.

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Rassilon@VERT/ECBBS to Digital Man on Fri Mar 12 06:27:20 2010
    Re: socket.recvline() and file_utime()
    By: Digital Man to MCMLXXIX on Thu Mar 11 2010 15:12:08

    Sorry, I know it's off-topic but I just couldn't help myself.

    Snapple "Real Fact" #18:
    A jellyfish is 95% water.

    Jellyfish heaven where jellyfish go...to get away from Mormons & drunk Eskimos....

    (Had to)

    -Rass...

    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
  • From MCMLXXIX@VERT/MDJ to Digital Man on Fri Mar 12 17:51:00 2010
    Re: socket.recvline() and file_utime()
    By: Digital Man to MCMLXXIX on Thu Mar 11 2010 15:12:08

    Re: socket.recvline() and file_utime()
    By: MCMLXXIX to Digital Man on Thu Mar 11 2010 01:22 pm

    file_touch("test.txt");
    log("original mod_time: " + file_date("test.txt"));
    log("changing file mod_time to 1267455497"); file_utime("test.txt",1267455497,1267455497);
    log("new file mod_time: " + file_date("test.txt")); file_remove("test.txt");

    OUTPUT:

    3/11 01:10:51p Node 1 original mod_time: 1268331052
    3/11 01:10:51p Node 1 changing file mod_time to 1267455497
    3/11 01:10:51p Node 1 new file mod_time: 1267455498

    It's driving me insane.. doesn't make sense

    What filesystem is "test.txt" being stored on? Some filesystems (e.g. FAT, FAT32) only support 2-second granularity for file date/times.

    Here's a Microsoft article on the subject:

    http://msdn.microsoft.com/en-us/library/ms724290%28VS.85%29.aspx


    ----------------------------------------------------

    var sock=new Socket();
    sock.bind(10088);

    Don't bind specific port numbers for outbound connections (as we discussed).

    sock.connect("localhost",25);
    log(time());
    log("connected: " + sock.is_connected);
    log("nonblocking: " + sock.nonblocking);

    OUTPUT:

    3/11 01:19:09p Node 2 1268331549
    3/11 01:19:09p Node 2 connected: true
    3/11 01:19:09p Node 2 nonblocking: false
    3/11 01:19:10p Node 2 null
    3/11 01:19:10p Node 2 1268331550

    -------------------------
    also driving me insane..

    does anyone have an insight on these things?

    unless I'm missing something, the sock.recvline() should wait 10 seconds before moving on, but it doesnt.

    I guess you didn't paste all your code - there was no call to recvline() the

    digital man


    turns out I was wrong anyway.. surprise surprise!
    though I still can't duplicate that actual example. I swear it happened



    ---
    þ Synchronet þ The BRoKEN BuBBLE (MDJ.ATH.CX)