While waiting for the SQL problems to get resolved, I’m using local databases for log processing. In doing that, I have noticed that updates for logs of huge sizes sawmill creates a temporary “update” directory in the same location as the primary database. If space is thin, this can fill the file systems and you can guess what happens.
My question is, since I’m using a UNIX operating system and some of the problems with rename vs. move regarding physical file systems, is there a way to tell sawmill to drop this temporary content to a location other than that of the primary db?
1. "RE: Temporary "update" directory location"
In response to message #0
You can change where the Database directory can be located, however, the temporary directory does not have a configuration item to specify a "new" temp location.
Printer-friendly copy
