I have an application where data are being collected
every 2-10 minutes, stored in a compressed format
on a remote machine and I need to collect and store them in a mysql database. To do that
I use perl net::telnet and net::ftp modules to
run the decompression(this is not a standard zip/gzip compression) on the remote server, then ftp the resut
, parse and store in the database. The parser does effectively a df -h to see if I am running out of
disk space before proceeding. When I first tried this,
my / partition was getting full because of temporary files
being written to it.(when I logged out the / size was restored to its normal size).[As I understand temporary files are essential for recovery, so one should not suppress them even if one could]. After a crash due to effectively
a hardware 'power' settigng that was telling the system to
go on suspend mode after some period of inactivity
I did various cleanups and now the size of /
no longer increases. This should be good news, but I'd like
to know why this happened, so this will not happen again.
Besides these problems, I was thiking of using LVM,
the question is has anyone tried it with Mysql? LVM is related in the sense that the advice to Logical Volume manager beginners is to keep root off LVM, but if root
will grow due to temporary files, this is not helpful.
Thanks in advance,
svar
every 2-10 minutes, stored in a compressed format
on a remote machine and I need to collect and store them in a mysql database. To do that
I use perl net::telnet and net::ftp modules to
run the decompression(this is not a standard zip/gzip compression) on the remote server, then ftp the resut
, parse and store in the database. The parser does effectively a df -h to see if I am running out of
disk space before proceeding. When I first tried this,
my / partition was getting full because of temporary files
being written to it.(when I logged out the / size was restored to its normal size).[As I understand temporary files are essential for recovery, so one should not suppress them even if one could]. After a crash due to effectively
a hardware 'power' settigng that was telling the system to
go on suspend mode after some period of inactivity
I did various cleanups and now the size of /
no longer increases. This should be good news, but I'd like
to know why this happened, so this will not happen again.
Besides these problems, I was thiking of using LVM,
the question is has anyone tried it with Mysql? LVM is related in the sense that the advice to Logical Volume manager beginners is to keep root off LVM, but if root
will grow due to temporary files, this is not helpful.
Thanks in advance,
svar