Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in:
dbera has requested info.
** Changed in: beagle (Ubuntu)
Assignee: (unassigned) = dBera
Status: Unconfirmed = Needs Info
--
Beagle loses file index on restart
https://launchpad.net/bugs/90152
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
No it isnt normal. However, it could be that beagled in just wrapping up before
exiting. You can try the following.
$ tail -f ~/.beagle/Log/current-Beagle
This will keep printing whatever the log messages. Do a beagle-shutdown, see
what messages show up in the log. If beagle is in the middle of
The real problem may be my slow hard disks. The real time that beagle take
to finish is about 1 minute, in a normal work day, but the cpu time is about
10 seconds. Maybe the init script is sending SIGKILL to it very earlier. I'm
using beagle 0.2.16 and doing some tests, but still my index is ok.
Upstream is faster in exiting when SIGTERM is sent. If it persists, I
would be curious to know how long it is taking to exit after the signal
is sent ? In general, if beagle is in the middle of indexing a huge
file, it will finish that file and then exit.
--
Beagle loses file index on restart
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,
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
