HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Potential Bug with SAM
Operating System - HP-UX
1833873
Members
1569
Online
110063
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
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
02-21-2005 10:38 AM
02-21-2005 10:38 AM
Potential Bug with SAM
Can someone verify whether or not what I am seeing is a bug in SAM? On HP-UX 11i on a trusted system, a user account with user account setting from /usr/lbin/getprpw. mintm=0, exptm=-1, lftm=-1.
mintm=0 is No minimum time between password changes.
exptm=-1 is password expiration is not set. (will use default)
lftm=-1 is password lifetime is not set. (will use default)
A user account with these setting will expire when the password exceeds the system default password lifetime is exceeded. But the user account in SAM shows that the Password Aging is Disabled. Has anyone seen this before? Is there a patch that address this? Thanks.
mintm=0 is No minimum time between password changes.
exptm=-1 is password expiration is not set. (will use default)
lftm=-1 is password lifetime is not set. (will use default)
A user account with these setting will expire when the password exceeds the system default password lifetime is exceeded. But the user account in SAM shows that the Password Aging is Disabled. Has anyone seen this before? Is there a patch that address this? Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2005 10:48 AM
02-21-2005 10:48 AM
Re: Potential Bug with SAM
Sounds like the command is violating the global settings for the system.
If this is indeed the case we have a bug. It may already be fixed. Search the patch database for sam patches, read the notes and you may find your patch.
http://www2.itrc.hp.com/service/patch/mainPage.do
SEP
If this is indeed the case we have a bug. It may already be fixed. Search the patch database for sam patches, read the notes and you may find your patch.
http://www2.itrc.hp.com/service/patch/mainPage.do
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
02-22-2005 06:16 AM
02-22-2005 06:16 AM
Re: Potential Bug with SAM
I have tried patch PHCO_29249, but it did not correct the problem.
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