Re: I Want to Help

A little more information about the program, adze.
I was having problems with logfiles growing to large.
This was on an embedded systems operating remotely.
The normal mechanisms for handling logfiles were not working out.
In frustration I wrote this little program.
It is intended to be used as a writer of trimmed logs (an adze is a tool 
for trimming logs).
It adds information to an existing file (adds sounds like adze).
It uses file locks to prevent/syncronize access to the file by other 
adze processes.
This makes it possible for two process to write to the same logfile in a 
reasonable manner.
It is also possible to use an adze file as a persistent queue.
In other words, it is a handy lightweight tool in the tradition of cut, 
split, sort, etc.
If you are interested, I would be willing to prepare it for inclusion 
with the other fileutils.
Thanks

toby cabot wrote:

>On Wed, Sep 25, 2002 at 01:14:07PM -0400, Fredrick Paul Eisele wrote:
>  
>
>>I have written a file utility program.
>>It belongs to the type of programs such as cat, echo, cp, tee, tail,  etc.
>>It writes its standard input to a named file where the size
>>of that named file is limited to a maximum value.
>>It also knows how to dump a file thus created.
>>(I haven't got a tail equivalent dump working yet.)
>>The way it works is that it maintains length/position information
>>at the beginning of the file.
>>I thought about putting the program on sourceforge but it is a fairly
>>small code, as you can imagine, so would 'fileutils' be a better place?
>>If you don't agree can you make a recommendation?
>>    
>>
>
>Frederick,
>
>Thank you for your interest in helping the GNU Project!  adze looks
>like a useful utility, and I think that your hunch about fileutils is
>a good one.  Probably the best thing to do at this point is send an
>email to the [email protected] mailing list explaining adze and
>offering to add it to fileutils.  The maintainers will be in a better
>position than me to decide whether it makes sense to add as a
>standalone program, or perhaps fold the features of it into existing
>fileutils.
>
>Before you do, though, you might want to invest some time in learning
>more about the GNU project, its beliefs and its goals.  You can do
>this at the GNU project web page, http://www.gnu.org/.  The GNU
>philosophy pages are especially important since GNU is an organization
>that's centered around a common set of beliefs about Freedom as it
>applies to software.  If you expect that your contribution to GNU will
>involve writing code you should also read the GNU Coding Standards at
>http://www.gnu.org/prep/standards_toc.html.
>
>Please let us ([email protected]) know if we can be of further help.
>
>Regards,
>The GNU Project Volunteer Coordinators
>
>PS.  If you'd like to stay in touch with the GNU project, please
>subscribe to the info-gnu mailing list at
>http://mail.gnu.org/mailman/listinfo/info-gnu.  It's a low-traffic
>list with news and announcements about the GNU project.
>  
>