GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS hpux 10.20
Operating System - HP-UX
1854801
Members
24330
Online
104103
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
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
10-10-2002 05:22 AM
10-10-2002 05:22 AM
having some minor problems with NIS and groups, running 10.20 at the NIS master, and both 10.20 and 11 on the clients.
The client with hpux 11 works fine even thou theres no + in /etc/group.
But on the hpux 10.20 clients, groups doesnt work (except for the users primary group) (have tried +, +: and nothing at the end of /etc/group)
ypcat group works, ypmatch gropname group and ypmatch gid group.bygid works aswell.
grpck at the NIS master returns NULL login name for the groups that dont have any users specified in /etc/group.
The client with hpux 11 works fine even thou theres no + in /etc/group.
But on the hpux 10.20 clients, groups doesnt work (except for the users primary group) (have tried +, +: and nothing at the end of /etc/group)
ypcat group works, ypmatch gropname group and ypmatch gid group.bygid works aswell.
grpck at the NIS master returns NULL login name for the groups that dont have any users specified in /etc/group.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2002 06:01 AM
10-10-2002 06:01 AM
Re: NIS hpux 10.20
additional info: (hpux 10.20 NIS client)
newgrp (-) group passes without any messages if the user is a member of group, but if not a member it returns "Sorry", but the groups command still returns only the primary group after.
groups username returns the full list with all the groups that username is member of.
newgrp (-) group passes without any messages if the user is a member of group, but if not a member it returns "Sorry", but the groups command still returns only the primary group after.
groups username returns the full list with all the groups that username is member of.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2002 09:03 AM
10-14-2002 09:03 AM
Solution
Jim,
I've seen this behavior on some systems in the past and it is a real pesky issue to debug. Typicals include:
- Missing logingroup link. On older HPUX releases this allows a user to be member of muliplegroups.
- ln -s /etc/group /etc/logingroup
- NIS group map with blank line or entry too long (1023 characters)
ypcat -k group.byname > /tmp/groupmap
Run grpck /tmp/groupmap
Also check MOST carefully
for blank links,
for ANY special characters or bogus entry in vi, using "set list" command (set nolist when done)
I think you already said that you checked out the /etc/group
file on the NIS master, especially for ANY entries over 1023, right?
Hope this helps. If all else fails, the HP Response Center can help you via Instant Support.
-> Brian Hackley
I've seen this behavior on some systems in the past and it is a real pesky issue to debug. Typicals include:
- Missing logingroup link. On older HPUX releases this allows a user to be member of muliplegroups.
- ln -s /etc/group /etc/logingroup
- NIS group map with blank line or entry too long (1023 characters)
ypcat -k group.byname > /tmp/groupmap
Run grpck /tmp/groupmap
Also check MOST carefully
for blank links,
for ANY special characters or bogus entry in vi, using "set list" command (set nolist when done)
I think you already said that you checked out the /etc/group
file on the NIS master, especially for ANY entries over 1023, right?
Hope this helps. If all else fails, the HP Response Center can help you via Instant Support.
-> Brian Hackley
Ask me about telecommuting!
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 2026 Hewlett Packard Enterprise Development LP