Mailinglist Archive: opensuse-kde (119 mails)

[Randall R Schulz <rschulz@xxxxxxxxx>]

Will,

On Thursday 19 October 2006 01:31, Will Stephenson wrote:
> On Wednesday 18 October 2006 19:19, Randall R Schulz said:
> > ...
> > But now I'm curious whether there is a problem either in principle
> > or in practice with having two (or more) concurrent KDE logins to a
> > single account / home directory.
> >
> > ...
>
> It's not so much Don't Do It, as We Aren't Responsible If You Do.  I
> often log in quickly over NX when there is already a local session
> running, without problems.
>
> It's a very bad idea to run two kmails side by side on the same
> account, as the local mbox/maildirs are not built for concurrent
> access and the indices are mmap'ed for speed.  KMail checks for any
> instance already running and shows dire warnings, which you should
> heed.

For my scenario, that wouldn't happen, since I run KMail on only one 
machine.


> I'd also be careful about installing more software while using
> multiple logons, as kbuildsycoca would probably run simultaneously
> and might create a corrupt syscoca, leading to missing kpart/plugin
> errors etc.  Not 100% sure what it does in that case though.  Apps
> that use sqlite (amarok) might also have multiple access issues.

OK. Software installation is not too common an action, at least not once 
the system is up and running and configured as I want it. I don't do 
much media on my Linux systems. I have a Mac for that stuff...


> Also configuration file corruption is one thing, but you would
> definitely notice that if instance 2 quits after instance 1, any
> config changes made by instance 1 would be lost.

I guess the answer, if I want to make this a regular thing, is to simply 
avoid the multiple concurrent KDE logins thing.


> HTH

Yes, thanks.


> Will


Randall Schulz