There are 2 spots in the code where paths explicitly
start with /tmp (tclhttpd.rc and auth.tcl). This does not
work for Windows. On Windows we need c:/temp or
something similar (BTW, I chose the standard quick start
option, so I run it withour any further installation step).
(thl@gedas.de)
Logged In: YES
user_id=400048
Originator: NO
I found the very same problem. My solution would be to use the TEMP or TMP environment variables,
as that seems to be the policy under Windows. They typically point to some private temporary
directory.
Logged In: NO
It turns out that Tcl on Windows (at least on Win XP) can refer to a directory like C:\tmp simply as /tmp. So to make tclhttpd run "out of the box" all you need to do is create C:\tmp as usual. Then the references to /tmp in tclhttpd.rc and auth.tcl work without any changes. Thus Tcl interprets /tmp as C:\tmp.
John Cocke --- jcocke@as.arizona.edu
Logged In: NO
To my comment of 2008-25-2 I should have added the fact that the "/tmp" reference gets you to C:\tmp only if you're on the C: drive to begin with. Actually, if your current drive is, say, F:,
the /tmp reference will look for the directory F:\tmp.
John Cocke -- jcocke@as.arizona.edu
Logged In: YES
user_id=400048
Originator: NO
Actually, I have encountered serious problems with temporary files handled naively:
If you are on a network disk and have no write access to the root directory, you can not
create a directory "/tmp" if there is not one already. Hence the application will fail.