https://bugs.kde.org/show_bug.cgi?id=433204
--- Comment #18 from Peter Wibberley <p.wibber...@btinternet.com> --- (In reply to tagwerk19 from comment #17) Tagwerk19, Thank you for the suggestion. No need to kill the process, as it's dying anyway. You're not wrong about shedloads: over 20MB and 200,000 lines collected in just a few seconds. There's 11973 instances or 'inotify_add_watch', with an 'inotify_init1(IN_CLOEXEC) and an 'inotify_init()' very early on. There appears to be several phases with different clusters of error messages. And it ends with "+++ killed by SIGSEGV +++" and "Segmentation fault", which would seem to explain why it's not running for long. I don't want to burden you with megabytes of probably superfluous detail, but do you have any suggestions about how I should proceed? Thank you again, and regards P > I think that baloo_file watches directories (mostly) and not files. > > I get this info from a trick of killing the baloo_file process and starting > from the command line under strace. So... > > ps ax | grep baloo_file > kill ... > strace baloo_file > > This gives shedloads of information; details of every system call. You can > however see the "inotify_add_watch' calls for each individual directory and > their return values - which can either include a steadily increasing count > or the 'changes will be ignored' message. You should be able to see a bit > more about what's happening > > I haven't worked how to see what info is being passed to the > baloo_file_extractor process and what it is doing. I also haven't discovered > where baloo logs its activities, that would be good to know! -- You are receiving this mail because: You are watching all bug changes.
