Luca Falavigna wrote: > Did you check if new version fixed this bug? Yes, it works:
start: integrit -C /etc/integrit/fs/etc.conf -cu integrit: ---- integrit, version 4.1 ----------------- integrit: output : human-readable integrit: conf file : /etc/integrit/fs/etc.conf integrit: known db : /var/lib/integrit/etc.cdb integrit: current db : /var/lib/integrit/etc-current.cdb integrit: root : /etc integrit: do check : yes integrit: do update : yes integrit: checking for missing files -------------- missing: /etc/a_test_file p(644) u(0) g(0) z(0) m(20071207-041359) missing: /etc/a_test_file s(9c1185a5c5e9fc54612808977ee8f548b2258d31) integrit: current-state db RMD160 -------------- integrit: b05e561cf1b8068006651d3c209599fff2b6e944 /var/lib/integrit/etc-current.cdb exit: 1 Has the database or digest format changed since the 3.x version? I noticed on first run it reported: changed: /etc/fstab s(44e84037a3cfde435ae99f386153aab4314a7514:456a18968abed4e7da7aef0676deb9ea45899b99) for what appears to be every file on the monitored file system. No big deal. It's a one-time issue. Thanks for taking the time to do a back-port for me. -Tom -- incorrect exit code for missing files https://bugs.launchpad.net/bugs/155058 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
