Known Issues
General Differences Nevada vs. Nevada+Sparks
Generally speaking the sparks name service enhancements are intended
to be fully backward compatible with the existing Nevada code base.
Some of the key differences that should be noticed (excluding
per-user authentication support) is that in general all databases
are now cached by nscd.
However, this is not to say that all getXbyYs will be cached by nscd.
In particular getent operations are performed in nscd, but the results
are not currently cached.
Another difference that should be noticed is the behavior of the
LDAP backend w.r.t. connection usage with sparks. When nscd is enabled
the LDAP backend now multiplexes LDAP lookups through nscd through
LDAP connections reducing the per connection load on the directory server.
In per-user mode, this becomes one connection per user, per machine
plus one for host based accesses.
Other name service backends should not see a difference in connection
behavior.
Specific Issues
Please send all comments issues questions to sparks-discuss.