As several OSW Scripts require some manipulation of the /etc/inittab file (either manually or during automated installs), we felt it important to share some key information related to that file that has come to light in the development and release of swreview V3.0 and V3.1.

1. Please make sure that all commands in the /etc/inittab file are delimited by a newline character. Failure to have a newline character at the end of the last command in the /etc/inittab file will cause init to never finish executing the last command in the inittab file and cause boot problems on the server.
2. You can not have multiple Xvfb processes spawning the same display/screen number in that file. You can have different display/screen combinations being respawned if different resolutions are required for different programs, but trying to respawn the same display/screen number will cause the init process to loop up, taking a large amount of CPU time. Originally this was also thought to cause reboot problems, but it's now thought those are caused (or at least compounded) by a separate issue listed above.

Please check your /etc/inittab file for these issues. They could be present due to an installation bug that was present in swreview V3.0 or due to addition of entries in /etc/inittab/ for other reasons. To fix either of these problems, remove any extra Xvfb entries from the file and add a newline after the last command (a carriage return) as necessary and then run the /etc/telinit q command as root.