You can change the profile via the HMC web interface. Select the managed system, select the LPAR from the upcoming list (click the checkbox), use the upcoming ">>" symbol right to the LPAR name and select "profile". There you can change the profile - it won't have any immediate effect.
After that, log into the LPAR as root and execute
To shut down the system complete. Wait until the display on the HMC really shows the system to be off. Then power it on using the new profile, again by selecting ">>", then "Operations" and select the profile you changed from the upcoming dialogue.
I have forgotten password of the system.I am having SCO Unixware 2.1.2.I am trying to change the password of the system by booting it with boot floopy.I edited the shadow file and made the password field blank.But I am not able to login.When I try to change the password of root or any id using... (1 Reply)
On SunOS 5.8 I get an error when starting a large Java process with over 2Gb memory.
Error occurred during initialization of VM
Could not reserve enough space for object heap
When stopping several other Java processes we can start this process. This seems to indicate that we don't have... (11 Replies)
Hi all,
I just add in new cpu/memory module into SFV480 and unable to see new module on slot B. I already try many way like only 1 new module and swap the both module and boot up but still unable to see it.
If I only install the module into slot B, then the server is unbootable at all.
I... (1 Reply)
I 've one box with 16gb of RAM and top, vmstat showing 8712M free , i 'm unable to find which process is eating up rest of the memory , the system is not running anything at the moment. (14 Replies)
On SunOS 10 get an error when starting a large Java process with over 2Gb memory.
Error occurred during initialization of VM
Could not reserve enough space for object heap
i have 32G memory !! , swap = 31G
Please any advice !!! (3 Replies)
Hi
I am unable to view the output of sar file using below command
sar -f sar07, it is showing below error.
Invalid system activity file: sar07 (0x920)
above file is in location /var/log/sa
wheather for memory it is creating the file at different location? (1 Reply)
bash-3.00# passwd sami
New Password:
Re-enter new Password:
Dec 14 00:07:43 hack passwd: passwdutil: crypt_gensalt Invalid argument
passwd: Unexpected failure. Password database unchanged.
Permission denied
i got this error while i am change the user(sami) passwd. (3 Replies)
I need to change password of a non-root user on HPUX. Due to some local policy, it is not allowing me to do so. I need to keep same (previous) password, as that is application user. Can I bypass policy for this time, for this user somehow ? I am root on this machine.
# uname -a
HP-UX thprnv02... (3 Replies)
Hi Friends,
I have created a new user "admin". I would like to use it as root equivalent (can change root password). Now, I want to give uid=0 and gid=0 to act as root. can you help? usermod command is not updating uid.
/etc/passwd:
root:!:0:0::/:/usr/bin/ksh... (6 Replies)
Discussion started by: suresh3566
6 Replies
LEARN ABOUT REDHAT
pam_console
pam_console(8) System Administrator's Manual pam_console(8)NAME
pam_console - control permissions for users at the system console
SYNOPSIS
session optional /lib/security/pam_console.so
auth required /lib/security/pam_console.so
DESCRIPTION
pam_console.so is designed to give users at the physical console (virtual terminals and local xdm-managed X sessions by default, but that
is configurable) capabilities that they would not otherwise have, and to take those capabilities away when the are no longer logged in at
the console. It provides two main kinds of capabilities: file permissions and authentication.
When a user logs in at the console and no other user is currently logged in at the console, pam_console.so will change permissions and own-
ership of files as described in the file /etc/security/console.perms. That user may then log in on other terminals that are considered
part of the console, and as long as the user is still logged in at any one of those terminals, that user will own those devices. When the
user logs out of the last terminal, the console may be taken by the next user to log in. Other users who have logged in at the console
during the time that the first user was logged in will not be given ownership of the devices unless they log in on one of the terminals;
having done so on any one terminal, the next user will own those devices until he or she has logged out of every terminal that is part of
the physical console. Then the race can start for the next user. In practice, this is not a problem; the physical console is not gener-
ally in use by many people at the same time, and pam_console.so just tries to do the right thing in weird cases.
ARGUMENTS
debug turns on debugging
allow_nonroot_tty
gain console locks and change permissions even if the TTY's owner is not root.
permsfile=filename
tells pam_console.so to get its permissions database from a different file than /etc/security/console.perms
fstab=filename
tells pam_console.so to read the table of configured filesystems from a file other than /etc/fstab when scanning permsfile. This
file is used to map directories to device names.
FILES
/var/run/console.lock
/var/run/console/
/etc/security/console.apps
/etc/security/console.perms
SEE ALSO console.perms(5)console.apps(5)
/usr/doc/pam*/html/index.html pam_console_apply(8)
/usr/doc/pam*/html/index.html
BUGS
Let's hope not, but if you find any, please report them via the "Bug Track" link at http://bugzilla.redhat.com/bugzilla/
AUTHOR
Michael K. Johnson <johnsonm@redhat.com>
Red Hat 2000/7/11 pam_console(8)