Re: Nepomuk

[Andrew Reid <reidac@bellatlantic.net>]

> I didn't ask for it and I don't want it. So why do we have to have it? It
> hogs the CPU and has an enormous database. I certainly do not have enough
> file to justify a 60Mb database.
> 
> Is it possible to stop it from working in KDE? And what about nepomuk?
> I'd like to stop that too. Do I have to exit from KDE and use another
> desktop?


  You can kill nepomuk. 

  To do this for one account, go to:
 
  K -> System Settings -> Advanced -> Service Manager, 
 
and in the list of start-up services, uncheck "Nepomuk Search Module."
I also uncheck "Update Notifier", "Free Space Notifier", and 
"Network Status Daemon".

  Then, in K -> System Settings -> Advanced -> Desktop Search, 
turn everything off in the "Basic Settings" tab. 

  You may have to log out and log back in to have it all take 
effect, and of course this won't remove the database, it will just
shut off the services.


  If you want to do it programattically, the files you want are
all in ~/.kde/share/config.  You want kdedrc, nepomukserverrc,
and nepomukstrigirc, they're "ini-format" files with square-bracketed
headers and key-value pairs, you turn stuff off by setting it to
"false", of course.

 
  Where I work, we have a bunch of Debian/KDE workstations which
NFS-mount user home directories -- desktop search is a network
traffic disaster on the NFS server, so shutting this off is a 
pretty high priority for us.  
  What we actually do is, all the clients have KDEDIRS set in 
/etc/profile, pointing to /usr/local/etc/kde, and in there, there's 
a $KDEDIRS/share/config directory with kdedrc, nepomukserverrc,
and nepomukstrigirc with just enough settings to shut it off.
  In the KDE scheme, KDEDIRS entries override user settings, and
the KDEDIRS is root-owned, so it's difficult for users to turn it
back on.  I think it's actually possible, though, if the users 
undefine KDEDIRS in their user-specific profiles, that might 
get around it.  But, users also enjoy having the NFS server
actually work, so we've been OK so far.



> Algol 68 specialist

  This is why I mentioned the config-file and system-wide ways
to do it...

                                  -- A.

--
Andrew Reid / reidac@bellatlantic.net