RE: kde 2 and solaris problem
"Schwartz Jr, William H" <[email protected]>
| Newsgroups | gmane.comp.kde.non-linux |
|---|---|
| Message-ID | <[email protected]> |
ahh, that did it. One of my users has a different primary group than everyone else so when he's the one that creates that directory noone else can write to it. as the permissions are 775 on the directory. Perhaps I should just manually create that directory when the system boots and chmod 777 it. thanks, Bill -----Original Message----- From: Waldo Bastian [mailto:[email protected]] Sent: Monday, July 15, 2002 12:08 PM To: [email protected] Subject: Re: [Kde-nonlinux] kde 2 and solaris problem On Monday 15 July 2002 07:51 am, Schwartz Jr, William H wrote: > Every now and then one of our servers starts refusing kde logins. The > error message is: > > ----------------- > Error setting up inter-process communications. > > Could not read network connection list > /home/schwawh/.DCOPserver_neo_nc900_3.0 > > Check that dcopserver is running. > ----------------- > > Even on the servers that are working I don't see any dcopserver process. > What's really hung up on these systems and how can I reset it without > needing to reboot? You may want to check the contents of /tmp/.ICE-unix. Does deleting the files in there helps? The dcopserver is probably listed in the process list as "kdeinit: dcopserver" Cheers, Waldo -- [email protected] | SuSE Labs KDE Developer | [email protected] _______________________________________________ kde-nonlinux mailing list [email protected] http://mail.kde.org/mailman/listinfo/kde-nonlinux