Nepomuk loses its memory after session restart
I've just had the unfavorable experience that nepomuk has apparently
lost its memory after indexing 75.000 files. All I had to do was to
logout from the session and then start a new one. As nepomukservices had
bloated to 2GB of VM, I thought this a good idea.
In order to check whether only the full-text index is affected, I set
the rating and comment on a file and again restarted the session. Alas,
both were lost afterwards.
Am I having particularly bad luck here or are others seeing similar
things?
Michael
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
Reply to: