On Thu, 2009-04-30 at 07:45 -0700, Ian Dichkovsky wrote:
> Thank you for the advices.
> We have discussed NIS configuration with our SA gang. They changed line in
> /etc/nsswitch.conf from
> passwd: files nis
> to
> passwd: compat
>
> In this case test NonReentrantSyscalls passed success
Hello,
Robert Jordan wrote:
>
> Jonathan Pryor wrote:
>> Perhaps I'm mis-reading that, but it implies to me that if NIS is
>> configured properly getpwent(3) should actually return NIS entries, not
>> return the '+:...' record from /etc/passwd directly. (Does anybody have
>> NIS setup to see w
Jonathan Pryor wrote:
> Perhaps I'm mis-reading that, but it implies to me that if NIS is
> configured properly getpwent(3) should actually return NIS entries, not
> return the '+:...' record from /etc/passwd directly. (Does anybody have
> NIS setup to see what getpwent(3) actually does?)
On a we
On Mon, 2009-04-27 at 23:41 +0200, Robert Jordan wrote:
> Jonathan Pryor wrote:
> > So why do you have '+::' in your /etc/passwd to begin with? That's
> > not a valid entry anyway (no user id)!
>
> It's for NIS.
>
> '+::' -> include all users returned by the NIS passwd map.
> '-::' -
Jonathan Pryor wrote:
> So why do you have '+::' in your /etc/passwd to begin with? That's
> not a valid entry anyway (no user id)!
It's for NIS.
'+::' -> include all users returned by the NIS passwd map.
'-::' -> allow only local users.
'+robertj::' -> include only 'robertj'
'-r
So, in short: your /etc/passwd database is corrupt, and instead of
fixing the database you want to "fix" UnixUserInfo to ignore "invalid"
users, where "invalid" users are those with a name of "+". (And why
just "+", as opposed to any larger set of strings? Because that makes
things work with your
Hello,
While running class library tests in our Mono MIPS 64-bit port we have met a
failed test in Mono.Posix.
Here is stacktrace
sstetskov...@sca-m0n8 ~/mono_new/mcs/class/Mono.Posix $ make check
ok=:; make run-test-re
