Open itjustwerks opened 6 years ago
typically if you put them in /tmp it will be cleaned up by the OS any time the machine reboots
On Fri, Apr 27, 2018 at 7:31 AM, Nathan Jass notifications@github.com wrote:
I'm wondering why the "temp_data****.fdf" files stick around after a file has been processed. Is it possible to have them cleaned up so they don't consume space? I'm running this on a Google Cloud instance, and would prefer not to have to worry about growing disk space. I would just schedule a job to remove them all at some interval, but I wouldn't want to delete one that was in use by a current processing job. Thoughts?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pdffillerjs/pdffiller/issues/69, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIMdn8vEAryskuKs4ErEjELyDlcB2K_ks5tsw-cgaJpZM4TqSfV .
-- Martin Murphy Whiteboard-IT http://whiteboard-it.com w: (205) 588-7102
@soitgoes How can you control where are going to be created?
I'm wondering why the "temp_data****.fdf" files stick around after a file has been processed. Is it possible to have them cleaned up so they don't consume space? I'm running this on a Google Cloud instance, and would prefer not to have to worry about growing disk space. I would just schedule a job to remove them all at some interval, but I wouldn't want to delete one that was in use by a current processing job. Thoughts?