I'm baffled where gettyset actually comes from... in any case, the there are error messages coming from gettyset since we moved from RHEL 5 to RHEL 6. Machines with console redirection on ttyS0 seem to end up working OK, but I have new machines where the console is on ttyS1. No booting info shows up and no agetty is started on these machines. If I ssh in and run gettyset by hand I get this:
root@cave018 ~]# /etc/init.d/gettyset initctl: Env must be KEY=VALUE pairs initctl: Env must be KEY=VALUE pairs [root@cave018 ~]# With -xv option the relevant trace lines look wrong. Not sure what they should look like... + '[' console == console -a console=ttyS1,115200 '!=' console=tty0 ']' echo $i | cut -d= -f 2 ++ echo console=ttyS1,115200 ++ cut -d= -f 2 + VALUE=ttyS1,115200 echo $VALUE|cut -d, -f 1 ++ echo ttyS1,115200 ++ cut -d, -f 1 + COTTY=ttyS1 echo $VALUE|cut -d, -f 2|cut -dn -f 1 ++ echo ttyS1,115200 ++ cut -d, -f 2 ++ cut -dn -f 1 + COSPEED=115200 + echo ttyS1,115200 + grep n8r + '[' -x /sbin/initctl ']' + initctl emit --no-wait fedora.serial-console-available ttyS1 115200 initctl: Env must be KEY=VALUE pairs ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
