SYSTEM Identifier not [1,4]
- From: sean@xxxxxxxxxx
- Date: Fri, 6 Jul 2012 08:07:33 -0700 (PDT)
OpenVMS 8.4 Integrity, patches current to update 6, migrated from Alpha system disk. We have found the SYSTEM identifier is not [000001,000004] as expected, but [000202,000005].
The SYSTEM account does have UIC [1,4].
(Cross posted from HP Support Forum)
My questions are:
What impact does having the SYSTEM identifier not be [000001,000004]?
What should we look out for when we change it?
On most systems, we have the account NDM_ADMIN that uses the same UIC as SYSTEM, namely [1,4].
Then we create an identifier, NDM_ADMIN (among other NDM identifiers), and grant it to SYSTEM, and the NDMADMIN account then also acquires the NDM_ADMIN identifier.
On one system, this fails. This is where the SYSTEM rights identifier is not [000001,000004] as expected, but [000202,000005]. There is an account with UIC [202,5], though there are no issues that we know of with that account.
On this system, after granting a rights identifier to SYSTEM, the NDMADMIN account does not acquire the identifier and cannot be used as it is on other systems.
We believe that this is caused by the fact the SYSTEM identifier is not the same as the SYSTEM account UIC, and that NDMADMIN also uses the SYSTEM UIC.. We tested this by deleting the NDMADMIN account using UIC [1,4], and copying the SYSTEM account to NDMADMIN using /UIC=[1,5], which was an unused UIC. We are then able to successfully grant the NDM_ADMIN identifier to the NDMADMIN account, and make use of the NDMADMIN account as expected.
- Prev by Date: Re: Poulson 6 times more powerful than Tukwilla?
- Next by Date: Re: Poulson 6 times more powerful than Tukwilla?
- Previous by thread: Re: Ghostscript: template to search file-based resources
- Next by thread: Re: SYSTEM Identifier not [1,4]