Your message dated Sat, 17 Nov 2007 01:17:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#401280: fixed in osiris 4.2.3-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: osiris
Version: 4.2.0-2
Severity: important
Tags: patch


            hy,

here is a mail from one of the developers with an temp. fix.

------------------------schnippp-----------------------------------------
In src/libosirisctl/osirisctl.c:ctl_get_database() at the break; on line
3808, the status should be set to TRUE when the function returns,
however on some systems a FALSE is returned to the calling function
src/cli/osiris.c:process_print_db() at the if statement on line 2867.

This causes the CLI print-db to fail even though the temporary database
was correctly written to the CLI host as shown by trying to diff the
db.temp and the original DB on the management host.

When debugging this issue, I found that putting a sleep(1); right before
the offending break in osirisctl.c on line 3808 fixes the problem.  Can
anyone provide insight as to why this workaround works, and maybe
provide a better fix?

This condition exists on some Debian systems as reported by Ruben
Puettmann and I was able to recreate the error on a Fedora Core 5 i386
virtual machine.

Thank you!

dave
------------------schnapp---------------------------------------

You can follow the discussion on:

http://osiris.shmoo.com/pipermail/osiris-devel/

attached is an Patch for the 4.2.2 Version

            Ruben


-- 
Ruben Puettmann
[EMAIL PROTECTED]
http://www.puettmann.net
--- osiris-4.2.2/src/libosirisctl/osirisctl.c   2006-07-27 19:57:51.000000000 
-0400
+++ osiris-patched/src/libosirisctl/osirisctl.c 2006-11-29 15:50:11.000673960 
-0500
@@ -3804,8 +3804,21 @@
                     }
                 }
                             
+                /* set status to TRUE, close the database file, and return
+                   to the CLI...
+
+                   This is functionally equivalent to what was previously here;
+                   however, some systems would see ctl_get_database() return
+                   FALSE to the CLI which would make print-db fail.
+                */
                 status = TRUE;
-                break;
+
+                if( dbfile )
+                {
+                    fclose( dbfile );
+                }
+
+                return status;
             }
 
             /* drop all other message types. */

--- End Message ---
--- Begin Message ---
Source: osiris
Source-Version: 4.2.3-1

We believe that the bug you reported is fixed in the latest version of
osiris, which is due to be installed in the Debian FTP archive:

osiris_4.2.3-1.diff.gz
  to pool/main/o/osiris/osiris_4.2.3-1.diff.gz
osiris_4.2.3-1.dsc
  to pool/main/o/osiris/osiris_4.2.3-1.dsc
osiris_4.2.3-1_i386.deb
  to pool/main/o/osiris/osiris_4.2.3-1_i386.deb
osiris_4.2.3.orig.tar.gz
  to pool/main/o/osiris/osiris_4.2.3.orig.tar.gz
osirisd_4.2.3-1_i386.deb
  to pool/main/o/osiris/osirisd_4.2.3-1_i386.deb
osirismd_4.2.3-1_i386.deb
  to pool/main/o/osiris/osirismd_4.2.3-1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jamie Wilkinson <[EMAIL PROTECTED]> (supplier of updated osiris package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 17 Nov 2007 12:02:15 +1100
Source: osiris
Binary: osirismd osiris osirisd
Architecture: source i386
Version: 4.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Jamie Wilkinson <[EMAIL PROTECTED]>
Changed-By: Jamie Wilkinson <[EMAIL PROTECTED]>
Description: 
 osiris     - network-wide system integrity monitor control interface
 osirisd    - network-wide system integrity monitor scanning agent
 osirismd   - network-wide system integrity monitor central management daemon
Closes: 345257 380178 398358 401280
Changes: 
 osiris (4.2.3-1) unstable; urgency=low
 .
   * New upstream release.
   * Added lsb sections to the initscripts.
 .
 osiris (4.2.2-1) unstable; urgency=low
 .
   * New upstream version.  (Closes: #398358)
   * Bug fix: "race Condition in osiris console", thanks to Ruben Puettmann
     (Closes: #401280).
   * Bug fix: "osirisd: unable to scan alot of directories", thanks to
     [EMAIL PROTECTED] (Closes: #380178).  Removed --chuid osirisd so that it
     can run as root and do its own privilege separation.  Necessary to
     actually scan the filesystem :)
 .
 osiris (4.2.1-1) unstable; urgency=low
 .
   * New upstream version.
   * Close old bug by virtue of the NMU diff being included.  (Closes: #345257)
Files: 
 5909d537fd436f42c1edcb4c0057980d 604 admin optional osiris_4.2.3-1.dsc
 1951c7dc0fe729af9ffaf58910340d12 1924149 admin optional 
osiris_4.2.3.orig.tar.gz
 1a8a3a5a281ef839082e31a511011019 10489 admin optional osiris_4.2.3-1.diff.gz
 6ab91e87c0e051f6196e5ff229d6af13 397056 admin optional osiris_4.2.3-1_i386.deb
 e4fb524a06ebf241ee6cb3135a3cce70 64226 admin optional osirisd_4.2.3-1_i386.deb
 c096886e0afbfa9ea9a75d62ae4b365b 408074 admin optional 
osirismd_4.2.3-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHPj/C5u9oNyz9HDgRAggYAKCN9yMS/7Vm5Mspnn0bgV5fBzo5YACfVFdb
p0rhOVFNdUldzFvwUlf43VI=
=vac8
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to