The logging is a problem - the problem is that most code carps liberaly to the logs,
and the logs have no clear logging levels. this should be fixed sometime in the
future. in the meantime you can use logrotate to rotate the logs daily, weekly,
monthly, every 3.71 days if you like - that's the "right way(tm)" of rotate logs - the
Jakartha way is so anoying, as I can't control when the rotation occures, how many
backlogs I keep and I also cannot compress the old logs - all these options (and more)
are available under logrotate, just don't forget to send HUP to the boxes after
rotation.
--
Oded Arbel
m-Wise Mobile Solutions
[EMAIL PROTECTED]
Mobile: +972-67-340014
Tel: +972-9-9581711 (ext: 116)
::..
narcolepulacyi, n.:
The contagious action of yawning, causing everyone in sight
to also yawn.
-- "Sniglets", Rich Hall & Friends
> -----Original Message-----
> From: Alex Judd [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 06, 2002 5:25 PM
> To: [EMAIL PROTECTED]
> Subject: Kannel log rotation
>
>
> Has anyone looked into making the logging in Kannel (at file
> level at least)
> a little more intelligent than it is at the moment? Currently
> even in info
> mode it generates fairly large logs which require continued sorting.
>
> One suggestion I thought was to adopt the Apache Jakarta
> project format of
> rolling the logs over every 24 hours into a new dated version
> so that at
> least this way they are in more maneageable chunks.
>
> I'm yet to play with the mySQL installation of logging
> however to the best
> of my knowledge this doesn't do this either.
>
> Alex
>
> ---
> http://www.skywire.co.uk/
>
>
>
