Thanks for making this clear! I don't know where the "-- MARK --" in my /var/log/messages comes from (do you know?) but I can confirm now that it's defenitly not logprof who makes them!
But wouldn't it be good if logprof had the ability to make marks? I mean why is someone using logprof? For updating a profile which was to strict or simply to check if the profiled application tried something which is not allowed or? So after someone checked logprof and did some rule changing this should be marked imo because if he tries to update later the profile of another app he gets asked for the same things of the first app again. My workaround now is simply to manually add a mark to /var/log/messages like simply a new line with the word: MARK. If I now execute "sudo logprof -m MARK" logprof acts correctly and ignores everything before. But one thing is important to mention: logprof doesn't look for the last mark but for the first!! So if you have: AA-complainlog1 MARK AA-complainlog2 MARK and do logprof -m MARK, logprof will react on the AA-complainlog2 because he just ignores everything before the first MARK found and not the last MARK in /var/log/messages so you have to use everytime another string as MARK. Is this a correct behavior? greets -- logprof doesn't handle marks (in any usefull way) https://bugs.launchpad.net/bugs/173260 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
