Skip to main content
Question

TEMP Space getting too big - Workspace Runner with Zip output

  • February 7, 2019
  • 1 reply
  • 12 views
H
Forum|alt.badge.img

Hi,

 

my workspace runner sends off a job to a child process which grabs files from a file system and zip them together.

The files are being copied to a temp location such as E:\\Temp\\_auto_zip_dataset_1549542585771_21996 but they don't clean up after the child process is done with the zipping job and the zip file is written into a desired output location.

Could you please suggest how to make sure the temp location doesn't run out of space?

Thanks, Monika

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

andreaatsafe
Safer
Forum|alt.badge.img+14
  • andreaatsafeSafer
  • Safer
  • 450 replies
  • February 12, 2019

Hi @honkovam,

For the temp location, is this set with the FME_TEMP environment variable? Or is this a temporary space you are writing the files directly to before zipping up the files?

Are you able to share both your workspaces (parent and child) with us?

- Andrea

Community Stats

32,083
Posts
121,826
Replies
39,717
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.