I was just looking at my logs.

My server_binkp.log goes back to december of last year. It is 77MB in size with 1,357,254 lines in it.

I have to do some trimming.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

Gryphon wrote to All <=-

My server_binkp.log goes back to december of last year. It is 77MB in size with 1,357,254 lines in it.

LOL I've been monitoring them as well and although mine are not that
old/big, they do grow fast. If things are running smoothly, I'll delete
them every once in awhile to keep them at a manageable size. I also
keep mutil to log level 1 unless I am having issues or testing.

Kev

___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A31 (Raspberry Pi)
* Origin: Razor's Domain 3.141592... (21:1/162)

On 09/22/16, Gryphon said the following...

I was just looking at my logs.

My server_binkp.log goes back to december of last year. It is 77MB in size with 1,357,254 lines in it.

I have to do some trimming.

I am sure there are others just like you. :P

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Twinkle BBS (21:1/126)

On 09/22/16, Gryphon said the following...

My server_binkp.log goes back to december of last year. It is 77MB in size with 1,357,254 lines in it.
I have to do some trimming.
--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

Sounds like a good use of a cron job every so many months, quarterly? Always best to make these things automatic once you find them. Perhaps an auto log clean out for all logs? Or zip them up and clear it out? They are text.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 09/22/16, bcw142 said the following...

On 09/22/16, Gryphon said the following...

My server_binkp.log goes back to december of last year. It is 77MB i size with 1,357,254 lines in it.
I have to do some trimming.

Sounds like a good use of a cron job every so many months, quarterly? Always best to make these things automatic once you find them. Perhaps
an auto log clean out for all logs? Or zip them up and clear it out?
They are text.

I can use logrotate, but I'll have to kill the mis job in order to do that. MUTIL has a log trimming feature, but there's nothing like that on any of the server_* logs.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (21:1/120)

bcw142 wrote to Gryphon <=-

Sounds like a good use of a cron job every so many months, quarterly? Always best to make these things automatic once you find them. Perhaps
an auto log clean out for all logs? Or zip them up and clear it out?
They are text.

For Linux, you could incorporate them into your logrotate configuration.


... This login session: $13.99, but for you $11.88
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

Gryphon wrote to bcw142 <=-

I can use logrotate, but I'll have to kill the mis job in order to do that. MUTIL has a log trimming feature, but there's nothing like that
on any of the server_* logs.

Well, you could define that time as an event to kick users off. It would be nice if you could send a signal (say USR1) to MIS to tell it to close the log file and open a new one.


... I'm working on my master's thesis on Amish road rage.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)