Hi, Frank

Thanks a lot.
I will patch webalizer with this option and will contact upstream.

Regards,
JOse Carlos

2006/3/24, Frank IJskes <[EMAIL PROTECTED]>:
> Package: webalizer
> Version: 2.01.10-26
> Severity: normal
>
>
> I found an issue with the way webalizer handles the configuration
> options.
>
> In the /etc/webalizer.config:
>  Incremental Yes
>
> The crontab job said:
>  webalizer -p -c /etc/webalizer.config
>
> and still, there was no incremental update.
> After examining the source file webalizer.c:
> i found the line:
>  case 37: incremental=(value[0]=='y')?1:0;
>
> This explained that Yes is not a usable option, but yes is.
> This case-sensitivity is not mentioned in the docs, nor handled in the
> processing of the config file.
>
> I read that others had a problem that might be related to this:
> bugs reported under nr 333801 / 311340 / 307705 might be solved with
> this case-issue / lack of documentation.
>
> In my opinion it might be wise to update webalizer.c to also allow
> capital y. Something like:
>  change  case 37: incremental=(value[0]=='y')?1:0;
>  to      case 37: incremental=(value[0]=='y' || value[0]=='Y')?1:0;
> And then of course for all the other options as well ;-)
>
>
> Frank IJskes
>
>
> -- System Information:
> Debian Release: 3.1
>   APT prefers testing
>   APT policy: (500, 'testing'), (90, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.14-2-686
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>
> Versions of packages webalizer depends on:
> ii  debconf                       1.4.30.13  Debian configuration management 
> sy
> ii  libc6                         2.3.6-3    GNU C Library: Shared libraries 
> an
> ii  libdb4.2                      4.2.52-18  Berkeley v4.2 Database Libraries 
> [
> ii  libgd2-noxpm                  2.0.33-1.1 GD Graphics Library version 2 
> (wit
> ii  libpng12-0                    1.2.8rel-1 PNG library - runtime
> ii  zlib1g                        1:1.2.3-9  compression library - runtime
>
> -- debconf information excluded
>
>

Reply via email to