Thanks for your answer. Normally I don't quit my apps with SIGKILL, but in this case appear that beagle isn't exiting cleanly. When I sent SIGTERM to it, several times it take a lot to shutdown. I guessing it don't is exiting cleanly on restart, because of this I report its the same with SIGKILL, forcing it to not exit cleanly.
Now I'm using upstream beagle, and i will report if anything changes. But the real problem with Edgy's version in my system is, beagle don't exit cleanly a lot of times. Sorry for my english. On 06/03/07, dBera <[EMAIL PROTECTED]> wrote: > > kill -9 (kill -SIGKILL) should never be sent to any program which is not > hanged. Ever tried sending SIGKILL to any filesystem or kernel process ? > You should use SIGTERM or SIGINT. kill -9 can not be handled by the > process and so beagle exits with an inconsistent state. Even if the > issue in the gnome bug is fixed, there is a high chance that after > kill-9, your existing index will have to purged and everything re- > indexed. > > On a different note, why do you have to restart beagle ? Note that, > besides SIGINT and SIGTERM beagle ships with the command beagle-shutdown > to stop beagle. > > -- > Beagle loses file index on restart > https://launchpad.net/bugs/90152 > -- Beagle loses file index on restart https://launchpad.net/bugs/90152 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
