I a full partition system (p510, AIX 5.3) I have:
# lscons
NULL
I've assigned a console:
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
chcons: console login enabled, effective on next system boot
chcons: console log assigned to /var/adm/ras/conslog, effective on next system b
oot
chcons: console logging enabled, effective on next system boot
chcons: console log size changed to 32768, effective on next system boot
chcons: console tagging disabled, effective on next system boot
After the change,
# lscons
NULL
# lscons -b
/dev/vty2
#
1) Is the reboot really needed? If yes, why? If not, what is a workaround?
It is a bit annoying and I have no green light for rebooting the server withing next few months. (I am not able open VTERM from a HMC, the system is in full partiotion mode/configuration)
2) What entries should exist in /etc/inittab to have vterm working? (right now after the console assigning I have the following entries "off")
# grep -e ^vt -e ^cons /etc/inittab
vty2:2ff:/usr/sbin/getty /dev/vty2
cons:0123456789ff:/usr/sbin/getty /dev/console
3) Which of these entries are needed there? Is there any manual modification required in /etc/inittab?
On the other system where vterm access works there is:
# grep -e ^vt -e ^cons /etc/inittab
cons:0123456789:respawn:/usr/sbin/getty /dev/console
4) There are two defined vty's and third, vty2 is "Available". How to get only vty0 Available in the system? After "rmdev" all of them will cfgmgr recreate only vty0 or it will have to be added from "smitty tty"?
# lsdev -CH|grep vt
vty0 Defined Asynchronous Terminal
vty1 Defined Asynchronous Terminal
vty2 Available Asynchronous Terminal
thx in advance,
r,m.
# lscons
NULL
I've assigned a console:
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
chcons: console login enabled, effective on next system boot
chcons: console log assigned to /var/adm/ras/conslog, effective on next system b
oot
chcons: console logging enabled, effective on next system boot
chcons: console log size changed to 32768, effective on next system boot
chcons: console tagging disabled, effective on next system boot
After the change,
# lscons
NULL
# lscons -b
/dev/vty2
#
1) Is the reboot really needed? If yes, why? If not, what is a workaround?
It is a bit annoying and I have no green light for rebooting the server withing next few months. (I am not able open VTERM from a HMC, the system is in full partiotion mode/configuration)
2) What entries should exist in /etc/inittab to have vterm working? (right now after the console assigning I have the following entries "off")
# grep -e ^vt -e ^cons /etc/inittab
vty2:2ff:/usr/sbin/getty /dev/vty2
cons:0123456789ff:/usr/sbin/getty /dev/console
3) Which of these entries are needed there? Is there any manual modification required in /etc/inittab?
On the other system where vterm access works there is:
# grep -e ^vt -e ^cons /etc/inittab
cons:0123456789:respawn:/usr/sbin/getty /dev/console
4) There are two defined vty's and third, vty2 is "Available". How to get only vty0 Available in the system? After "rmdev" all of them will cfgmgr recreate only vty0 or it will have to be added from "smitty tty"?
# lsdev -CH|grep vt
vty0 Defined Asynchronous Terminal
vty1 Defined Asynchronous Terminal
vty2 Available Asynchronous Terminal
thx in advance,
r,m.