Your message dated Fri, 31 May 2013 07:17:14 +0200
with message-id <[email protected]>
and subject line Re: Bug#627415: aide: AIDE aborts on $ I think
has caused the Debian Bug report #627415,
regarding aide: AIDE aborts on $ I think
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
627415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627415
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aide
Version: 0.15.1-3
Severity: normal

Got this email this morning after I had installed Horde from PEAR. /tmp is a 
symlink to /dev/shm/tmp so the directory in question is /tmp/buildd.

******************************************************************************
*IDE returned with exit code 137. AIDE returned an unknown non-zero exit valu*
*                             exit value is 137                              *
******************************************************************************
AIDE post run information
output database /var/lib/aide/aide.db.new was copied to /var/lib/aide/aide.db 
as requested by cron job configuration
End of AIDE post run information

Errors produced  (2 lines):
Error in selective regexp: 
/dev/shm/tmp/buildd/php5-5\.3\.3/pear-build-download/Horde_ActiveSync-1\.0\.0/test/Horde/ActiveSync/{137c3bb0-838d-499a-9f0e-fb6c0761da51}1$
Killed

End of AIDE error output.

funny, AIDE did not leave a log.
=======
I have !/dev in my local aide config so it shouldn't even go down that path. 
Also it should not be doing anything with the file names and it looks like it's 
doing variable expansion or something.


-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aide depends on:
ii  aide-common        0.15.1-3              Advanced Intrusion Detection Envir
ii  bsd-mailx          8.1.2-0.20100314cvs-1 simple mail user agent
ii  liblockfile1       1.08-4                NFS-safe locking library, includes
ii  ucf                3.0025+nmu1           Update Configuration File: preserv

Versions of packages aide recommends:
ii  cron                          3.0pl1-116 process scheduling daemon

aide suggests no packages.

-- no debconf information





--- End Message ---
--- Begin Message ---
Version: 0.15.1-4

Hello,

On Fri, May 20, 2011 at 01:18:27PM +0100, Tim Phipps wrote:
> Got this email this morning after I had installed Horde from PEAR.
> /tmp is a symlink to /dev/shm/tmp so the directory in question is
> /tmp/buildd.
> 
> ******************************************************************************
> *IDE returned with exit code 137. AIDE returned an unknown non-zero exit valu*
> *                             exit value is 137                              *
> ******************************************************************************
> AIDE post run information
> output database /var/lib/aide/aide.db.new was copied to /var/lib/aide/aide.db 
> as requested by cron job configuration
> End of AIDE post run information
> 
> Errors produced  (2 lines):
> Error in selective regexp: 
> /dev/shm/tmp/buildd/php5-5\.3\.3/pear-build-download/Horde_ActiveSync-1\.0\.0/test/Horde/ActiveSync/{137c3bb0-838d-499a-9f0e-fb6c0761da51}1$

This error was caused by the 70_aide_dev script, which generated an
individual rule for each file in /dev but didn't escape the '{' and '}'
characters. This script was replaced by a single native aide rule in
0.15.1-4. Hence I close this bug now.

Best regards

Hannes

--- End Message ---

Reply via email to