Here's two bugs I've just logged...

1) Using the korn shell (ksh) for a console install of ColdFusion MX will fail when it gets to the password step. The installer tries to do some tricks to hide the password from displaying, and the console "freaks out". Use sh or bash instead.

2) On Solaris, setting the ColdFusion user, i.e. nobody, to have a login shell of /bin/false will prevent ColdFusion MX from starting. Setting the user login shell to /bin/false effectively prevents a real user login for that account. This is a common practice to increase security for server daemons.

bash-2.03# usermod -s /bin/false nobody
bash-2.03# cat /etc/passwd | grep nobody
nobody:x:60001:60001:Nobody:/:/bin/false
bash-2.03# /opt/coldfusionmx/bin/coldfusion start
Starting ColdFusion MX...
There may be a few moments before you can access the ColdFusion MX administrator. This is normal.
There has been an error starting ColdFusion MX, please check the logs.
bash-2.03#