Bug 63697
Summary: | setnetgrent() returns wrong status value when netgroup exists | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <michael.gerdts> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | drepper, fweimer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-19 11:49:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2002-04-17 15:24:47 UTC
But glibc documents the current behaviour: When the call is successful (i.e., when a netgroup with this name exists) the return value is `1'. When the return value is `0' no netgroup of this name is known or some other error occurred. Note that e.g. AIX/BSD/Darwin don't return anything from setnetgrent and endnetgrent, so relying on specific return value without checking it in configury is wrong anyway. Very well. After going through the pain of using info, I found that this is indeed documented. We really need info2man or a hack on man that will bring up the appropriate info node (as a man page rather than in info) as part of its search path. |