Just to note about gwlib/log.c:output() and gwlib/accesslog.c:alog()
functions which IMHO is a base for the whole logging and both of them
uses platform's standard version of vfprintf implementation which
sometimes is buggy, slow and so on.

Apache uses it's own snprintf and clones implementation and you can
find the whole list of different implementations and their comparison
here:

http://www.and.org/vstr/printf_comparison

Shall Kannel implement it's own implementation or maybe one defined at
compile time?

On 10/10/05, Mindaugas <[EMAIL PROTECTED]> wrote:
>
> >   Trying to debug performance problems with wapbox I looked into OProfile
> > output. And some numbers
> > look a bit high. E.g. isn't computer spending too much time in vfprintf()
> ?
> > I looked into source
> > code and is really fflush() after vfprintf() so needed? I have nothing
> > against losing few lines of
> > logs after computer crash.
>
>  So no ideas about fflush()? And how to debug "stuck" Kannel from my
> previous
> post? I could even give access to offending system.
>
>  Mindaugas
>
>
>


--
Dziugas

Reply via email to