Mailinglist Archive: opensuse (3964 mails)

[Anders Johansson <andjoh@xxxxxxxxxx>]

On Monday, 1 November 2004 16.29, SRGlasoe wrote:
> On Mon November 1 2004 9:06 am, Anders Johansson wrote:
> > On Monday, 1 November 2004 15.57, SRGlasoe wrote:
> > > My resolution so far is to reboot. Neither a login/logout of the user,
> > > a restart of kdm/X has worked. This happens on several different
> > > machines with different versions of SUSE and KDE and kmail. All the
> > > same ISP with different user accounts. I haven't narrowed it down any
> > > more than this. It took quite a long time to get this far.
> >
> > Hmm. Is nscd running? If it is, the next time it happens, try shutting it
> > off (rcnscd stop) instead of rebooting
>
> nscd is running. What's the theory?

the theory is that something about your system changes that is so severe that 
a simple log out/log in won't cure it. I'm not saying it *definitely* is, but 
nscd is the usual suspect in these cases. Something that it caches changes, 
and since your system gets it from nscd instead of from the actual source, it 
doesn't see the change. Stopping nscd forces your system to get the real data 
from the actual source

If it doesn't work, we'll have to come up with a second theory, but for now 
this is my guess

> I will try your suggestion IF it ever 
> happens again. Could be months, could be today, could be tomorrow. I may
> have a way to produce the error "on demand" but it seems to require leaving
> kmail up and running overnight; system has to go through the midnight hour
> and any cron or other system checks that happen after midnight and are
> usually finished by 5AM.

Yeah, I hate those erratic errors that you never know when they'll happen. 
They're a real PITA to debug