The reason we found for this is that when you redirect the entire
Caches folder using Server Cleanup, it puts an alias to /tmp/xxxx
(xxxx = WGM User's ID number). The problem with this behavior (and
why Firefox appears to not want to open) is that this folder doesn't
exist on a particular computer when a user logs in (When I manually
through Terminal create the folder in that location, it now works).
That led us to the question as to how Server Cleanup intends for that
folder to be created on a computer when a user logs in, in order to
allow the Alias it creates to point to a valid location.
Since we ran this with his latest rev of the program (2.8.2b), we were
wondering what his response would be (i.e. a problem on his end with
the program or a problem with something on the server or client end of
things).
We could always create a little script that runs at startup to create
a folder in that location with the user's WGM user id number as the
name of it, but we thought it would be wise to ask him (the creator of
the Server Cleanup program) first.
Thanks for your time and consideration.
Personally, the option to direct the entire Caches folder is there
because it was asked for so many times. I personally prefer to
redirect only the folders that I need to.
Hope this helps clear a few things up.
On another note, since I am already addressing the entire list, Server
Cleanup 3 is in production. Now is the time to ask for any requests
for features.
Mark Gabrenas
Apple Certified Systems Administrator
m.gab...@mac.com