SUMMARY:Finger mechanism & problem

From: Robert Glover (
Date: Wed Sep 09 1998 - 20:20:20 CDT

Only one reply to this from David Blaine who pointed out that the remote
server side of finger is initiated by inetd. This is not the problem in my
case as I am running the command finger [username] on the local server.
In addition more than 90% of my users do return the correct information. Some
however return null values. Thanks anyway and I will keep searching.

Is anybody able to point me in the right direction to solve this problem?
System SparcServer 1000E Solaris 2.4 I have about 6000 users in a NIS+
environment. They can all log in without problems and can all be displayed
using the niscat command. However the command :- finger username does
not work for all users. For more than 90% of users it return the correct
information but for the rest it returns:-
Login name username In real life: ???
I have been unable to discover any difference between the NIS+ table entries
for the users who display correctly and those who do not. The nsswitch.conf
entry for passwd is :- files nisplus This is effecting one of our
applications which apparently uses a similar method to authenticate users.
The people for whom finger username does not work are unable to to log in to
the application. (Knowledge Engineering Texpress) Does finger username use
one of the getpwnam or getpwuid system calls and if so what could cause some
of the users to return a null value? I have looked on Sunsolve but can't find
a similar situation. Will summarise. Regards Rob

Rob Glover
Unix System Administrator
Western Australian Police Service
Phone +61 8 9222 1733
Fax +61 8 9222 1698

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:48 CDT