On Wed, 04 Mar 2009, Javier Fernández-Sanguino Peña wrote:

> On Wed, Mar 04, 2009 at 09:18:01PM +0100, Peter Palfrader wrote:
> > On Wed, 04 Mar 2009, Javier Fernández-Sanguino Peña wrote:
> > 
> > > On Sun, Oct 05, 2008 at 09:27:47PM +0200, Peter Palfrader wrote:
> > > > On any action from samhain I get these when run on an ia64 system like 
> > > > merulo
> > > > or caballero.
> > > 
> > > Version 2.2.3-6.1, uploaded October the 20th, fixed an alignment problem 
> > > in
> > > armel (#501231). Could you please tell me if this NMU fixes also fixes 
> > > this
> > > bug?
> > 
> > It did not:
> 
> Could you please install samhain-2.4.6a (from experimental) to see if the
> problems persist?

*cough*

wea...@merkel:~$ sudo dpkg -i samhain_2.4.6a-1_ia64.deb 
[sudo] password for weasel: 
(Reading database ... 61389 files and directories currently installed.)
Preparing to replace samhain 2.2.3-6.2 (using samhain_2.4.6a-1_ia64.deb) ...
Stopping file integrity checker: samhain.
Unpacking replacement samhain ...
Setting up samhain (2.4.6a-1) ...
Starting file integrity checker: assertion failed (x_dnmalloc.c): hashval < 
AMOUNTHASH
/etc/init.d/samhain: line 27: 20325 Aborted                 start-stop-daemon 
--start --quiet --exec $DAEMON
invoke-rc.d: initscript samhain, action "start" failed.
dpkg: error processing samhain (--install):
 subprocess post-installation script returned error exit status 134
Processing triggers for man-db ...
Errors were encountered while processing:
 samhain
wea...@merkel:~$ 
wea...@merkel:~$ 
wea...@merkel:~$ sudo /usr/sbin/samhain -t check -i -p err -s none -l none -m 
none                  
assertion failed (x_dnmalloc.c): hashval < AMOUNTHASH
zsh: abort      sudo /usr/sbin/samhain -t check -i -p err -s none -l none -m 
none


-- 
                           |  .''`.  ** Debian GNU/Linux **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to