On 01/25/2014 03:00 PM, Vince Radice wrote:
From my first post -
I am running Fedora FC19-64 bit. Libreoffice Version: 188.8.131.52
Build ID: 184.108.40.206-2.fc19
My Desktop is KDE 4.11.4
The problem is that if I don't keep deleting these empty files, they
will build up.
Depending on what filesystem you are using,
you could even run out of inodes on your disk even though you
may have plenty of storage space.
This happened to me on a little server here that's had ext3 since Lenny,
and for some reason there was no entry for popcon in /etc/logrotate.d,
and I ended up with some 50,000,000,000 something log files.
I couldn't write to the disk, even though df -h showed that I still had
like 20gb on the / partition and like 100gb on the /home
(lesson: rotate all log files, kids).
I first noticed this when looking through the log for my
backup program. There were over 250,000 files. I assume that the
overhead involved in a loist this size would be enourmous. I have also
had problems where the hdd activity was so great that I could not get
much response and started closing thing to try to figure out what the
problem was. Since I have been keeping the empty files deleted, I have
not had the problem.
multilingual web development
EN, ES, FR, PT
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy