Jigsaw on Macintosh

Jeff Dripps writes:
 > 
 > Problem #1: It appears that Jigsaw manages data files by first creating a
 > temporary file (with a .tmp extension), then after updating the file
 > contents, attempts to rename the file to the desired name. The problem is,
 > at least on macintosh, this fails to occur for some reason. After
 > exercising Jigsaw, I find various files scattered about, such as
 > realms.db.tmp, admin.db.tmp and many .jigidx.tmp files. It appears that
 > Jigsaw could not rename them for some reason (possibly because they are
 > open?). In any event, this does not appear to be due to a duplicate file
 > name, as in many cases there was no such file.

File renaming is one (and the only) place that I had to change to make
it work similarly on Unix and Windows. It moght be the case that it
needs another fix on the mac. The best way to solve this problem would
be to compile a simple program that uses the File.rename method, and
see how it performs (eg instead of running your system rename, write a
program that does File.rename and see how it goes). It might also be a
Java-mac bug (?)

This is the one I used on windows (from memroy)

import java.io.*;

public  class Rename {
    public static void main(String args[]) {
        try {
            File from = new File(args[0]);
	    File to   = new File(args[1]);
	    if ( ! from.rename(to) )
	        System.out.println("rename "+from+" to "+to+" failed !");
        } catch (Exception ex) {
            ex.printStackTrace();
            System.out.println("Rename <from> <to>");
        }
    }
}

 > Problem #2: Rarely will Jigsaw ever finish sending a lengthy html page (or
 > the browser somehow is missing the last block??). For example, the URL:
 > http://www.macalot.com:9999/User/Tutorials/configuration.html
 > will rarely finish. It gets to 90-99% and just hangs, as though the browser
 > is waiting for one more block.

Have you tried telneting to the server ? I am a bit helpless here
since it looks to me like some Mac-related problem (?) What I would do
is first turn of keep-alive (as you did, to be sure that this is not
the problem), then by telneting to the server,see what it sends you
back. It might be the case that some flush call is missing (such as a
flush before the connection is closed - That s the only thing I can
think of)

Anselm.

Received on Monday, 8 July 1996 10:42:27 UTC