HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- finger command returns multiple people
Operating System - HP-UX
1833187
Members
2991
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2000 08:16 PM
11-29-2000 08:16 PM
When I run the 'finger' command on some of my boxes, I sometimes get multiple responses. These responses aren't of the same person, but of different people. I've checked their password entry and I can't see anything untoward - uid are unique, shells are valid etc. Has anyone else experienced this or know what causes this? Thanks.
This space intentionally left blank.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2000 08:55 PM
11-29-2000 08:55 PM
Solution
I found a similiar case in the database:
Problem:
Running the command finger(1) with no options and a username as an argument returns extra, unexpected results:
$ finger b4901
Login name: b9401
In real life: test bod
Directory: /home/b9401 Shell: /usr/bin/sh
Never logged in.
No Plan.
Login name: bsmith
In real life: B Smith
Directory: /home/bsmith Shell: /bin/sh
Never logged in.
No Plan.
In this case the user bsmith was unexpected. bsmith's details appear in addition to the correct details.
Using the -m option returns only the desired user.
RESOLUTION
The extra entry is seen because of the way in which finger(1) performs its search.
With the -m option the search is confined to the user name. In the above example only b4901 would be matched.
However without this option the search also checks the real name field of /etc/passwd for the argument. As real names do not contain numbers, finger(1) strips these from the argument before performing a case-insensitive search.
Hence in the above example the search through the real name field is for b and not b4901. The search finds user bsmith, because their real name is set to 'B Smith' (the b is matched.)
There is not a single resolution for this issue, however the following points should be noted:
use finger -m to search using only the user name.
set real names appropriately. If the user's first name is not known then a solution would be to insert a period(.) instead of a space between initial and surname.
Hope that helps,
Steffi Jones
Problem:
Running the command finger(1) with no options and a username as an argument returns extra, unexpected results:
$ finger b4901
Login name: b9401
In real life: test bod
Directory: /home/b9401 Shell: /usr/bin/sh
Never logged in.
No Plan.
Login name: bsmith
In real life: B Smith
Directory: /home/bsmith Shell: /bin/sh
Never logged in.
No Plan.
In this case the user bsmith was unexpected. bsmith's details appear in addition to the correct details.
Using the -m option returns only the desired user.
RESOLUTION
The extra entry is seen because of the way in which finger(1) performs its search.
With the -m option the search is confined to the user name. In the above example only b4901 would be matched.
However without this option the search also checks the real name field of /etc/passwd for the argument. As real names do not contain numbers, finger(1) strips these from the argument before performing a case-insensitive search.
Hence in the above example the search through the real name field is for b and not b4901. The search finds user bsmith, because their real name is set to 'B Smith' (the b is matched.)
There is not a single resolution for this issue, however the following points should be noted:
use finger -m to search using only the user name.
set real names appropriately. If the user's first name is not known then a solution would be to insert a period(.) instead of a space between initial and surname.
Hope that helps,
Steffi Jones
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP