Hi all

If I understand previous correspondence correctly - this newly released version of sarg should overcome all the difficulties building it for RHEL5. If so - could someone with more packaging experience than I - give it a try? The current rpmforge version is fairly broken and causes lots of kernel errors in my logwatch.

Richard.



-------- Original Message --------
Subject:        [orso] sarg 2.2.7 released
Date:   Sat, 06 Feb 2010 23:48:23 -0000
From:   plorso <[email protected]>
Reply-To:       [email protected]
To:     [email protected]



Hi,

sarg-2.2.7 released:

Feb-05-2010 Version 2.2.7
                - Extra compile and run time protection (FORTIFY_SOURCE) fixed 
in configure.
                - Use tabulations as columns separator in intermediary files to 
avoid problems when a field of the log contains a space.
                - Input log file type detection partly rewritten to clearly 
distinguish which type is processed where.
                - Read the input log file from standard input if log file name 
is -.
                - Use string pointers in getword instead of copying the strings 
over and over.
                - Use LC_TIME to format some dates and times in the report 
according to the selected locale.
                - Sarg.conf can list up to 255 access.log files.
                - Downloaded files suffixes are matched against a sorted list 
and use a dichotomic search.
                - Added getword_atoll to read a number directly from a file 
without an intermediary string storage.
                - Use boolean to enable the options instead of string compares.
                - Accept an absolute path for the language file in sarg.conf.
                - Experimental: Can show the backtrace of the program when a 
getword loop is detected to help in locating the origin of the error.
                - Protect the creation of the index against invalid directories.
                - Only copy the files (not the subdirs) when creating the 
directory with the images to include in the reports.
                - Directories deleted without using the rm system command.
                - Index created using an internal sort algorithm instead of a 
system call.
                - Fixed Debian bug #408577 (changed exclude_hosts to exclude 
subdomains and IPv4 subnets).
                - Replace --enable-htmldir by --enable-sargphp to avoid 
confusion on the name (thanks to Peter Nixon).
                - Installation of sarg-php can be disabled with 
--disable-sargphp.
                - Fixed empty entries in squidGuard log when the URL doesn't 
start with protocol://.
                - Fixed regressions in creation and reading of a sarg parsed 
log (thanks to Joao Alves).
                - Does not report URLs consisting of only a host name ending 
with .com as a downloaded file.
                - Mangle the $ and @ signs in user ID to make the resulting 
file name valid in shell commands.
                - Fixed a regression in the default value of --enable-sargphp.
                - Increase the maximum size of a line read from access.log and 
detect longer lines that were silently splitted in previous versions.
                - Tolerate longer URLs during the reading of the access.log to 
have less chances of aborting during that phase. It only helps if short URLs 
are output in the reports. If long_url is set, sarg will still abort on over 
sized URLs.

http://sarg.sf.net

Many thanks to Frédéric Marchal
Pedro Orso



------------------------------------

For more information: http://sarg.sourceforge.net
Post message: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List owner: [email protected] Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://groups.yahoo.com/group/orso/

<*> Your email settings:
   Individual Email | Traditional

<*> To change settings online go to:
   http://groups.yahoo.com/group/orso/join
   (Yahoo! ID required)

<*> To change settings via email:
[email protected] [email protected]

<*> To unsubscribe from this group, send an email to:
   [email protected]

<*> Your use of Yahoo! Groups is subject to:
   http://docs.yahoo.com/info/terms/


_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users

Reply via email to