Re: NIS (client) issues...
From: Howard J. Rogers (hjr_at_dizwell.com)
Date: 08/27/04
- Next message: kwswz_at_whwjzt.com: "Re: NIS (client) issues..."
- Previous message: nosy: "Re: KDE 3.3 ** New ** Packages Tonight - Here's the scoop"
- In reply to: Howard J. Rogers: "NIS (client) issues..."
- Next in thread: mhaxqpw_at_xnasbx.com: "Re: NIS (client) issues..."
- Reply: mhaxqpw_at_xnasbx.com: "Re: NIS (client) issues..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Aug 2004 13:41:42 +1000
Howard J. Rogers wrote:
> I'm trying to set up a NIS server (success, after patching). And a NIS
> client laptop. Both using Suse 9.1 Professional. I've read the NIS How-To.
> And I've looked in the Suse administrator's guide. And I've searched
> Google for exactly the error text I include below... all to no effect.
> I've done it just as the documentation said to do it, and its not having
> the desired effect!
>
[snip]
>
> There was an error setting up inter-process communications for KDE. The
> message returned by the system was: Could not read network connection
> list //.DCOPserver_shostakovich__1. Please check that the "dcopserver"
> program is running.
>
> (Shostakovich being the laptop's hostname).
>
> And:
>
> Will not save configuration
> Configuration file "//.kde/share/config/ksplashrc" not writeable
> Configuration file "//.kde/share/config/kdeglobals" not writeable
>
> The KDE splash screen then just sits there, and I have to
> Ctrl+Alt+Backspace to return the login prompt, where I can correctly log
> in as (local) root.
>
[snip]
As a bit of a follow-up to my own post, but still seeking clarification on
procedures, if I log any of the network users in using TWM instead of KDE,
they can do so, and can navigate network shares etc. So the network
authentication side of things actually seems not to be the issue. It's a
KDE thing, then, I guess.
Also: once I've logged someone in using TWM, and try and run Konqueror, KDE
throws a bunch of error messages as before. So, I became root, manually
created a (for example) /home/howardjr directory and chmod'd it 777 (just
in case). And tried running Konqueror again... and this time it worked,
creating a bunch of directories it needs to be happy.
Log out and log that same user back in using KDE, and now KDE is happy. And
you'd never know there'd been a problem.
So it's clearly a permissions and a directories thing.
If I log onto a, ahem, Windows workstation that's part of a Domain as a new
user, Windows chugs away for a while creating a bunch of directories for
the new user's profile to occupy. Do I take it that NIS does not work this
way? That I must manually create the /home/username directories myself
before the first log on? And if so, what would be a good set of chmod
numbers to set for such a home directory. 777 is a bit of an opening
gambit, I realise. :-)
Sorry if this is all stupidly obvious to NIS old timers.
Regards
HJR
- Next message: kwswz_at_whwjzt.com: "Re: NIS (client) issues..."
- Previous message: nosy: "Re: KDE 3.3 ** New ** Packages Tonight - Here's the scoop"
- In reply to: Howard J. Rogers: "NIS (client) issues..."
- Next in thread: mhaxqpw_at_xnasbx.com: "Re: NIS (client) issues..."
- Reply: mhaxqpw_at_xnasbx.com: "Re: NIS (client) issues..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
