Description of problem: 
Have a fairly conventionall 00webalizer cron.daily script to handle multiple webalizer runs specifying a different conf file via "-c" option for each run, where functional part of bash script is
...
for i in /etc/webalizer/*.conf
  do 
     /usr/bin/webalizer -Q -c $i     
  done
 
This worked under Fedora 17 and earlier releases, but under Fedora 19 (with the default /etc/webalizer.conf file renamed and the "-Q" replaced with "-v") webalizer produces the message:
"Error: Unable to open configuration file /etc/webalizer/webalizers.conf", where the indicated path and file is what was passed on the "-c" option, with similar failures for all other conf files in /etc/webalizer directory.  Other messages follow that confirm the intended output directory, history file, and hostname are not being used, proving that the intended conf while was indeed not processed.  The access attributes including SE context on the conf files in question are identical with those on the default installed /etc/webalizer.conf file.  Tried changing the script to change to directory /etc/webalizer and pass webalizer just the file name, but that failed with similar messages.  The only way I could get this to function was to copy each conf file in succession to the default webalizer conf files /etc/webalizer.conf and invoke webalizer without any "-c" option, as in
...
for i in /etc/webalizer/*.conf
  do 
     /bin/cp -f --preserve=timestamps $i /etc/webalizer.conf
     /usr/bin/webalizer -v 
  done



Version-Release number of selected component (if applicable):
webalizer-2.23-05


How reproducible: 100%


Steps to Reproduce:
1.Rename original /etc/webalizer.conf file
2.Create /etc/webalizer directory containing webalizer conf file(s) with unique names
3. Invoke webalizer from a cron script with 
for i in /etc/webalizer/*.conf
  do 
     /usr/bin/webalizer -Q -c $i     
  done

Actual results:
"Error: Unable to open configuration file <-c- option-filenamepath-here>"

Expected results:
Alternate conf file specifed in -c option should have been used as if it were in /etc/webalizer.conf and no "-c" option was specified.

Additional info:
I suspect this might be reproducible without using cron scripts, but since my objective was to get this working under cron and there might have been something significant with that environment, all my testing was in that environment.