Bug 3940 – hosts allow can't use netgroup

Bug 3940 - hosts allow can't use netgroup

Summary:	hosts allow can't use netgroup

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	tcp_wrappers (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-07-07 17:09 EDT by glenn
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-08-23 17:31:31 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description glenn 1999-07-07 17:09:43 EDT

Use of netgroups in the hosts allow directive can't be used
since they aren't configured.  With debug level set to 3,
the following message appears in /var/log/samba/log.smb:

[1999/07/07 15:40:08, 0] lib/access.c:string_match(95)
  access: netgroup support is not configured

This is due to a failure of the configure script to search
libnsl.a for the yp_get_default_domain() function.

A workaround is to define

export LDFLAGS=-lnsl

prior to running the configure script.

Comment 1 clemons 1999-07-09 11:48:59 EDT

Actually, this should be classified as  a more general problem as I
have the same difficulties with sshd and tcp_wrappers.  Was netgroup
support not compiled in Red Hat binaries and, if so, is there an
explanation as to why not?

Comment 2 Bill Nottingham 1999-07-21 14:39:59 EDT

fixed in samba in 2.0.5-1, available RSN.
Changed to tcp_wrappers...

Comment 3 Jeff Johnson 1999-08-23 17:31:59 EDT

NETGROUP support added in tcp_wrappers-7.6-9.

Note You need to log in before you can comment on or make changes to this bug.