Problem with Scratch Directory

[Doug Foxgrover]

We are running OmniWeb 1.0 prerelease 1.  We have a license for 10 processes, a network of  13 NS machines, and lots  
of students who like the program (as do I).  The students all have their own individual accounts.  When one student logs  
on and starts OmniWeb, as soon as they get their first image, a new scratch directory gets created, /tmp/OmniWeb.  This  
directory has the ownership and permissions of this particular student, and everything works fine.  


When this student quits OmniWeb and logs out, the directory /tmp/OmniWeb remains, still belonging to this student.   
When a new student logs into this machine and starts OmniWeb, the new student cannot use the default scratch  
directory, because it is not world writable.  Therefore, the new student cannot view images or otherwise use the scratch  
directory.

Can you please return to using /tmp as the scratch directory?  Or have the directory /tmp/OmniWeb deleted when the  
app quits?  I realize there are other fixes (teaching all the students to change the scratch directory for themselves,  
creating a /tmp/OmniWeb directory with root ownership and world rw privileges every time the computer boots up), but  
it's a lot of work for those of us that have multiple users per machine, and I'm not sure what the benefit is in having an  
OmniWeb subdirectory of /tmp.

Thanks for the great product!

D. Foxgrover
Lab Manager
Physics and Astronomy
Carleton College
dfoxgrov at physics.carleton.edu