[Koha-bugs] [Bug 14321] Merge UploadedFile and UploadedFiles into Koha::Upload

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14321

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #92 from David Cook <dcook at prosentient.com.au> ---
Just a FYI for people testing out permanent uploads.

If you're using "/tmp" as the "upload_path", you might want to check if you're
using "PrivateTmp". I'm using openSUSE 13.2 and when I look at
/usr/lib/systemd/system/apache2.service, I see "PrivateTmp=true". I think that
file is located elsewhere on Debian, but I'll leave that up to others to find
that.

In any case, instead of creating
"/tmp/koha_upload/36411ad1c1adeb6d0d774f5282fe8790_test1" when permanently
uploading a file, it creates
"/tmp/systemd-private-bf25b4b0e5994604b54422ea98e4b8c8-apache2.service-PJS1uF/tmp/koha_upload/36411ad1c1adeb6d0d774f5282fe8790_test1".

Fortunately, as far as I can tell, this doesn't create a problem for Koha, at
least in the short run. While Koha might still think it's looking in
"/tmp/koha_upload", it's actually looking in
"/tmp/systemd-private-bf25b4b0e5994604b54422ea98e4b8c8-apache2.service-PJS1uF/tmp/koha_upload".

But of course if you go looking for a file in "/tmp/koha_upload", you're going
to be looking for a long time.

Of course, you'd never actually use "/tmp" for storing a file permanently, as
"/tmp" should be deleted when your server next reboots (or if some other
clean-up job is running). 

If you do something like /home/dcook/koha/uploads, you'll be fine. The file
will be stored where you expect it to be stored.

Not a problem, but just a FYI to developers and testers.

-- 
You are receiving this mail because:
You are watching all bug changes.