Bug 82565

Summary: Commands that access group names fails when NIS group is large
Product: [Retired] Red Hat Linux Reporter: Morten Finborud <morten.finborud>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: fweimer, mitr
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-10 23:09:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Morten Finborud 2003-01-23 14:34:06 UTC
Description of problem:
Commands accessing group names fails when the group name is a nis group spread 
over several entries (due to the number of members in group). Only the group id 
is returned from commands like groups or ls -la

ypcat group |grep :1300:
hda:!:1300:a110915,a108743,a100141,u21081,a793918,<lotta more names>
hda2:!:1300:a113014,a794279,a793203,a792412,a455915,<lotta more names>

Version-Release number of selected component (if applicable):
sh-utils 2.0.12

How reproducible: 100%

Steps to Reproduce:
1. groups a100141

Actual results:

id: cannot find name for group ID 1300
id: cannot find name for group ID 3100
id: cannot find name for group ID 1668
id: cannot find name for group ID 102
id: cannot find name for group ID 2020
id: cannot find name for group ID 2800

Same happens when doing a ls -la   (group name does not appear)
-rw-rw----    1 a100141  1300           91 Jan 23 14:54 group.txt   

Expected results (as on a RedHat 7.3 installation):

a100141 : hda nho_tavd petro utfo dip ios ediv hdaunix irap recall lmadmin sd ut
fit charisma    

-rw-rw----    1 a100141  hda           91 Jan 23 14:54 group.txt   

Additional info:

This works perfect on RedHat 7.3

Comment 1 Tim Waugh 2003-01-23 16:32:52 UTC
I think this is fixed for future releases.

Comment 2 Jakub Jelinek 2003-04-10 23:09:19 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.