UNIX FM5.5.6 /tmp directory error

["Ede, Craig" <craig.ede@xxxxxxxxxxxxx>]

Framers,

I'm getting a lot of errors involving .fm* directories in /tmp while running fmbatch scripts in FM5.5.6.

The errors typically read something like:
rmdir: directory "/tmp/.fmU2g3SUL.xxx": Directory not empty.
In many cases the named directory contains a file called 1.printerlist

Can anyone give me a clue as to how to prevent the condition that is causing the directories to be retained so that I can remove this noise from my log files?

Probably a more general question is: Where is the behavior of these /tmp/.fm* dirs defined in the documentation for FrameMaker. Some things I know: Such .fm* directories are created and removed dynamically as FM opens and closes files Three such .fm* directories are created in /tmp by default or in the directory pointed to by the environment variable TMPDIR if you choose to define that. One of them holds (copied) graphics data, cached out of the document and held in this directory until the document is closed and written out. In FM5.0/5.1, running out of space on /tmp while writing these graphics resulted in 0 byte files being written as the files are opened and then reinserted in the document when saving/closing. This was one cause of the gray box syndrome. [Zero bytes means no graphic!] In FM5.5 you get a error message saying graphic info has been lost, but no clue as to why that is and how it relates to the .fm* dirs.

Any tips on the specific question in paragraph 3 would be appreciated. In addition to the script log noise, I have multiple users using dozens of shared licenses on a single (very fast!) server. They encounter such errors because everyone is logging in remotely and then FM attempts to write all these directories and files to the single /tmp dir on that server.

Thanks.

Craig
Los Jugadores Bazutadores

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **