2.0.3 spamming logfile with nsswitch warning

jimp

1.) Were the original nsswitch.conf settings wrong?

Probably, but the way 2.0.1 was built the problem was masked/hidden.

2.) Were the nsswitch warnings serious or could the have been ignored and what did the warnings mean?

Harmless log spam.

3.) Why did pfSense 2.0.1 not show those warnings? I suppose 2.0.1 had the same e.g. original nsswitch.conf settings but cannot verify anymore.

There was a problem with the way the system was being built up until a week or two before 2.0.3 was released, so options in the build system to disable unneeded components of the base OS were being ignored in some cases. As a side effect of this, OpenSSL wasn't updating/working properly until we fixed it on 2.0.3 and 2.1.

The default nsswitch.conf on FreeBSD 8.1 apparently had the compat & nis bits in it. The default one on 8.3 (used for pfSense 2.1) just had 'files' there. We don't include nor need nis, so leaving it out is OK.

We just didn't catch that error on 2.0.3 in remote syslog before the release. It's a fairly easy fix for those who need it though, manually edit the file or gitsync to RELENG_2_0 to pick it up.

pvoigt

Thank you, Jim, for your explanations making me at least feel a bit wiser :)

RonpfS

Would a system patch be created?

jimp

@RonpfS:

Would a system patch be created?

See the last line of my last post.

RonpfS

@jimp:

See the last line of my last post.

I didn't know what gitsync meant :-[

I did the gitsync that also fix the ntp server timeout … great tool ;D

Thanks for all