On 2008/06/30 23:14, Rildo Cezar wrote: >> I got this error on Sarg running on 4.3 amd64: >> >> SARG: sarg version: 2.2.3.1 Jan-02-2007 >> SARG: Maximum file descriptor: cur=128 max=1024, changed to cur=20000 >> max=20000 >> SARG: Reading access log file: /var/squid/logs/access.log >> SARG: (util) tbuf=30Jun2008, reading: 0.00% >> SARG: (util) period=30Jun2008- >> SARG: Records in file: 1163, reading: 100.00% >> SARG: Records read: 1163, written: 1163, excluded: 0 >> SARG: Squid log format >> SARG: (util) data=30/06/2008 >> SARG: (util) tbuf=30Jun2008 >> SARG: (util) period=30Jun2008-30Jun2008 >> SARG: Period: 30Jun2008-30Jun2008 >> SARG: pre-sorting files >> SARG: (util) dirname=/var/www/htdocs/sarg/30Jun2008-30Jun2008 >> SARG: (util) wdir=/var/www/htdocs/sarg/30Jun2008-30Jun2008 >> SARG: Making period file >> SARG: Making file: /tmp/sarg/127.0.0.1 >> SARG: Sorting file: /tmp/sarg/127.0.0.1 >> SARG: Reading DansGuardian log file: /var/log/dansguardian/access.log >> SARG: Sorting file: /tmp/sarg/dansguardian.log >> Segmentation fault (core dumped) >> >> I can run fine on i386. Problem is only on amd64.
sarg 2.2.3.1 was definitely not 64-bit clean. -current has sarg 2.2.5 which includes a fixes for one problem on amd64 (fixed in 2.2.4), but it's quite likely that there are more.
