Hi tim,

In what way is log rotation not applicable to your problem? It could
compress or delete older log data regularly...

About an external program, rsyslog comes to mind (has multiple sources and
sinks for log data and can also do log rotation). There may be smaller
solutions that I just don't know.

https://www.rsyslog.com/doc/v8-stable/tutorials/log_rotation_fix_size.html

Kind regards,
Jakob


Am Sa., 10. Dez. 2022 um 02:03 Uhr schrieb tim Rowledge <tim at rowledge.org>:

> I spent way too long failing to find the right search phrase, so maybe
> somebody here knows sometihng to get me started.
>
> My server system is writing a *lot* of output to a file via the Toothpick
> package's FileLogger class. I mean, like a GB/hr. I can turn it down but
> then I don't see the stuff that explains why it went boom. Evidently
> naively writing to a file and watching it with `tail -f` isn't the best
> idea here but all I'm spotting on the google is lots of  'use logrotate'
> stuff that doesn't seem to be applicable at all.
>
> Is there some technique I can use that lets me write out stuff and watch
> it without it filling up my little SSD? Some way to specify a file that has
> a maximum size and that dumps the older stuff as more is added? Some
> program I can pipe data to that keeps a limited set of messages?
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Useful random insult:- Calls people to ask them their phone number.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221210/636ab118/attachment.html>