HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Query On NIS
Operating System - HP-UX
1832299
Members
1936
Online
110041
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
06-27-2009 04:22 AM
06-27-2009 04:22 AM
My query is we have NIS environment with 2300 unix users.We are going to implement password aging.
We are afraid that when multiple users change their password at the same time,can this lead to map corruption?
How the update happens in the map ?Is it one by one(serial) or simultenious ( parallel)?
We are afraid that when multiple users change their password at the same time,can this lead to map corruption?
How the update happens in the map ?Is it one by one(serial) or simultenious ( parallel)?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2009 10:27 AM
06-27-2009 10:27 AM
Solution
Shalom,
No, implementing aging on 2300 users at one time will not lead to corruption. The OS has safeguards and queues them up. The system may get a little sluggish at times but it will be handled. It is not a lot of i/o
SEP
No, implementing aging on 2300 users at one time will not lead to corruption. The OS has safeguards and queues them up. The system may get a little sluggish at times but it will be handled. It is not a lot of i/o
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2009 12:32 PM
06-27-2009 12:32 PM
Re: Query On NIS
Is there any document related to this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2009 11:09 PM
06-28-2009 11:09 PM
Re: Query On NIS
Hi,
this document (man-page)
http://docs.hp.com/en/B2355-90692/yppasswdd.1M.html
describes the arguments
-m NOPUSH=1
which I would use in such an environment:
So not each change of the passwd of a user will lead to map-updates in your whole environment.
Do these updates by a crontab entry. Inform your users, that their password-change will not be effective immediately but after a time gap (depending on your crontab setting).
mfG Peter
this document (man-page)
http://docs.hp.com/en/B2355-90692/yppasswdd.1M.html
describes the arguments
-m NOPUSH=1
which I would use in such an environment:
So not each change of the passwd of a user will lead to map-updates in your whole environment.
Do these updates by a crontab entry. Inform your users, that their password-change will not be effective immediately but after a time gap (depending on your crontab setting).
mfG Peter
The Universe is a pretty big place,
it's bigger than anything anyone has ever dreamed of before.
So if it's just us, seems like an awful waste of space, right?
Jodie Foster in "Contact"
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