I missed the original post -but maybe if u r referring to problems with 
managing such a huge log file, 
why not use a syslogd approach. it moves the /var/log/messages file to 
another filename so that each file is manageable and you can locate your 
info easily.
regards
-kamal




On Fri, 2003-06-13 at 04:53, der Mouse wrote:
> > I've got an application that generates logging events to a file--
> > this file continually grows and can consume over 1 Gbyte of disk
> > space.
> 
> > For my application, I will *never* read back the file,
> 
> If you will *never* read it, I have to ask, why bother writing it?
> Surely the most effective and efficient thing to do is to just
> altogether skip writing data that will never be read....
> 
Obviously its for logging as the poster said.
Application like an intrusion detection system may want to log alot of
data which can be analized on a different machine later.

Have you tried fsync ?
 

> /~\ The ASCII der Mouse
> \ / Ribbon Campaign
>  X  Against HTML                      mouse@rodents.montreal.qc.ca
> / \ Email!                  7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 
27 4B
>