[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-developers] Webilizer 2.01 PKG install -setupCountryResolves?



On Mon, 2001-12-31 at 12:55, Nigel Hewett wrote:
    Sorted.
    
     It looks as if the webalizer on my system didn't have dns support? So I
    followed the first part of this article
    http://list.cobalt.com/pipermail/cobalt-developers/2001-October/033965.h
    tml
     And re ran webalizer.pl which was modified to include the -N -D
    switches. Now resolving the names. 
    
    Thanks all you guys for help.
    
    Now if I wanted to upgrade from 2.06 - 2.09 would the only file be
    required webalizer from the bin package?
    
    Nigel
    
It should be.  If you read the article on webalizer 2.01 at
www.bearfruit.org, it tells you how to back up the current bin file and
use a symbolic link so that you can easily undo your changes if needed.
Matt
    -----Original Message-----
    From: Matthew Nuzum [mailto:cobalt@xxxxxxxxxxxxx] 
    Sent: 30 December 2001 19:20
    To: Cobalt Dev
    Subject: RE: [cobalt-developers] Webilizer 2.01 PKG install
    -setupCountryResolves?
    
    On Sun, 2001-12-30 at 07:30, Nigel Hewett wrote:
        Morning Mat,
         
         I have checked the /etc dir for webalizer.conf nothing same with
    locate
        webalizer.conf. So will this be correct syntax as per you doc:
         
        $messages .=
                   `webalizer -N 5 -D /home/webalizer/cache.dns -n $asite -s
        $asite -r $asite -q -T -o $thepath
            $prefix/$asit
            /logs/web.log`;
    Looks OK.   Make sure folder /home/webalizer exists.  Of course, make
    sure there are no unwated carriage returns.
        
        or
        
        Shall I create a conf file in /etc and have the contents :
        
        DNSChildren 5
        DNSCache /home/webalizer/cache.dns
        
        And nothing else?
        
        Thanks again
        
        Nigel
        
        -----Original Message-----
        From: Matthew Nuzum [mailto:cobalt@xxxxxxxxxxxxx] 
        Sent: 30 December 2001 00:58
        To: Cobalt Dev
        Subject: RE: [cobalt-developers] Webilizer 2.01 PKG install -
        setupCountryResolves?
        
        On Sat, 2001-12-29 at 16:45, Nigel Hewett wrote:
            Matthew,
            
            	Being a newbie I don't believe I have a conf file. This
    was
            installed via the web interface as a pkg and I have not done no
        more. I
            gather this is just run daily via the webalizer.pl in the
    section :
            
        You do, it's /etc/webalizer.conf I believe.  You can run the
    following
        command to find it:
        locate webalizer.conf
               $messages .=
                   `webalizer -n $asite -s $asite -r $asite -q -T -o
    $thepath
            $prefix/$asit
            /logs/web.log`;
            
            could I amend this to include the dns lookup? If so how?
        Yes you can.  The last link in my message has very clear
    instructions on
        what to do.  I personally prefer the webalizer.conf file but either
    will
        provide a workable solution.
            
        Matt Nuzum
        
            -----Original Message-----
            From: Matthew Nuzum [mailto:cobalt@xxxxxxxxxxxxx] 
            Sent: 29 December 2001 20:30
            To: Cobalt Dev
            Subject: Re: [cobalt-developers] Webilizer 2.01 PKG install -
    setup
            CountryResolves?
            
            On Sat, 2001-12-29 at 12:40, Hemant Arora wrote:
                Dear Nigel,
                
                As far as I know is you need to switch on the HostNameLookup
    ON
        in
                httpd.conf. By default its OFF and it records IP no's rather
        than
            domain
                name. Once its ON the next time webalizer generate the
    report It
            will show
                you the Country Pie chart.
            Yikes!  Don't do this, there's a better way.  If you do this,
    you
        will
            slow your server way down, and in some cases, people may not be
    able
        to
            see websites on your server! (for instance, reverse lookups fail
    or
        go
            very slow).
            
            All webalizer 2 versions have reverse DNS lookups built in.
        THerefore
            it will resolve the names in the logfile automatically when the
    log
            files are processed.  
            
            In your webalizer.conf file, set the following options:
            DNSChildren 5
            	You can go as high as 20 without too much problem.  
            	If you have 512 MB Ram or more do 20, otherwise do 5 -
    10.
            DNSCache /home/webalizer/cache.dns
            
            Those two options will cause webalizer to process the log files
        twice,
            once to resolve the IP address and store them in a cache file,
    the
            second time to create the reports as usual, using the DNS name
    in
        the
            cache instead of the ip address.
            
            Processing log files will take 2-3 times longer than normal, but
            hopefully you're processing your log files during your off peak
        hours.
            
            I documented this a while back at www.bearfruit.org and you can
    get
        more
            information at www.mrunix.com/webalizer and
            ftp://ftp.mrunix.net/pub/webalizer/DNS.README
            
            Matt Nuzum
        
            
            
            
        
        _______________________________________________
        cobalt-developers mailing list
        cobalt-developers@xxxxxxxxxxxxxxx
        http://list.cobalt.com/mailman/listinfo/cobalt-developers
        
        _______________________________________________
        cobalt-developers mailing list
        cobalt-developers@xxxxxxxxxxxxxxx
    http://list.cobalt.com/mailman/listinfo/cobalt-developers
        
        
        
    
    _______________________________________________
    cobalt-developers mailing list
    cobalt-developers@xxxxxxxxxxxxxxx
    http://list.cobalt.com/mailman/listinfo/cobalt-developers
    
    _______________________________________________
    cobalt-developers mailing list
    cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers