On Wednesday 18 October 2006 19:19, Randall R Schulz said:
I recently tried a FreeNX login as a potential fallback while I sort out a problem with a KVM switch with a poor implementation of its USB hub. NX seems to work quite well, at least over a 100 megabit LAN and it seems like a good solution (and a lot cheaper than a four-port DVI / USB KVM!).
However, as soon as I logged in, it occurred to me that I was already logged in directly to the same account on the target host. I quickly logged out of the NX session and have seen no evidence of any configuration file corruption from that brief login. prints 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.
If anyone has experience with or knowlege of this situation, I'd appreciate hearing it.
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. 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. 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. HTH Will