> > ....could this problem be nscd related?
> That would certainly explain the behavior, yes.
Just FYI nscd version on that unfortunate box is
nscd:
Installed: 2.3.6.ds1-8
Also I wasn't able to replicate the problem on up-to-date etch box (without
nscd)... nscd)... nscd)... nscd)... (waw... weird vim behavior)
And you are guys share the prize! the cause is indeed in nscd: problem goes
away if I stop nscd, and comes back when I start it. And it might be that
originally I didn't have nscd running, which is why I didn't observe this
behavior. nscd --debug didn't show anything interesting besides first hit
against not yet known sashroot and then requests to resolve uid=0.
Since, I assume, behavior of the system should be preserved while running nscd,
this issue is an nscd bug, since nscd changes the way uids get resolved.
Is that correct?
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
