On 6/20/11, Jerry Geis wrote:
> I have noticed that only around the 4am-4:15 time frame when the trim is
> happening does my
> other process log connection attempts but my process (forking and
> opening databases) is not responding in time to give data back
> to the connecting process. Not critica
On 6/20/2011 10:31 AM, Kai Schaetzl wrote:
> Jerry Geis wrote on Mon, 20 Jun 2011 11:05:34 -0400:
>
>> The trimmming of the log files is just so they they dont take a bunch of
>> space on the HD.
>
> use logrotate and zip them.
Not sure how that helps with the issue of queuing up a whole lot of di
Jerry Geis wrote on Mon, 20 Jun 2011 11:05:34 -0400:
> The trimmming of the log files is just so they they dont take a bunch of
> space on the HD.
use logrotate and zip them.
Kai
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mail
Jerry Geis wrote:
> hi all
>
> I have something like 3000 log files in a directory (from data
> collection).
> At 4am in the morning cron runs a script of mine that essentiallly trims
> all files in that directory back to a certain size.
> Basically does a "tail -c filename > tmp_filename"
>
>
Hello Jerry,
On Mon, 2011-06-20 at 11:05 -0400, Jerry Geis wrote:
> My question is how do I tell the script that runs to run at a lower
> priority perhaps ???
A similar issue came up just a few days ago.
$ man ionice
Regards,
Leonard.
--
mount -t life -o ro /dev/dna /genetic/research
_
hi all
I have something like 3000 log files in a directory (from data collection).
At 4am in the morning cron runs a script of mine that essentiallly trims
all files in that directory back to a certain size.
Basically does a "tail -c filename > tmp_filename"
I have noticed that only around
6 matches
Mail list logo
