-
-
Notifications
You must be signed in to change notification settings - Fork 761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/tmp-folder is being filled #50
Comments
Normally the /tmp folder is managed by the OS. But because other uses were reporting the same problems I've made a change so the package will explicitly remove it's temp files. Did you install v2.8.0? |
Hello, I'm also having this same issue. I've used this package for about 6 months and I have to (regularly) empty my I upgraded to 2.8.0 and still have the same issue. Here's what I'm seeing.
Emptied my
Excellent! Backup is done.
I go back into As @skovmand mentioned - I guess I could just set up a cron to delete it, but seeing as you mentioned it should delete the temporary file(s) now, I'm not so sure it's working. |
Thanks for your efforts testing this. I'll take a look at it soon and fix it. |
Version 2.8.2 should fix these problems. Please reopen this issue if your temp folder is still filling up. |
Will give it a go now as I'm free - reporting back in a moment :) |
Empty
Moment on truth...
Hmm - doesn't look like it's emptying still? Also, I'm unable to open as this isn't my issue - would you like me to open another or keep this in here? |
Mmmm, I'll review my code again. Are you sure you're using v2.8.2? |
Yep, as far as I know...
|
ok, i found another pesky bug. My tests show that in v2.8.3 there shouldn't be any file left by this package in the tmp folder. Could you please test it again? |
Perfect @freekmurze, just tested this and it's no longer leaving a trace in my |
Hi!
First of all thanks for your package. It's a great help for me.
My system dumps its database every hour and uploads to S3. It seems the package uses the
/tmp
folder for temporary files, but doesn't remove them afterwards. This means my drive is slowly filling up with files, eventually eating up all disk space (my db is about 200MB in size).Can you comment on this? Perhaps the problem lies elsewhere.
I know I can just make a cron job to delete the files, but I thought the problem might exist for others too.
My server setup is a Laravel Forge server (Ubuntu Linux 14.04, 40GB disk on DigitalOcean Amsterdam).
The text was updated successfully, but these errors were encountered: