Folks we are now delploying a lot of Erlang instances and we are seeing bugs been thrown and would like to examine them...
Normally we connect to the running instance with a remote shell and get access to an Erlang console that way, but this doesn't work for rb or error messages...
How do I get remote access to my SASL error messages without dropping the server, starting it non-detached and looking at the shell?
I ran into this back in R11B and ended up creating a clone of rb that works over a remote shell (http://github.com/archaelus/erms/blob/master/src/erms_rb.erl). The trick is to discover the group_leader of the caller and then send output there.
I should probably tidy that up and submit it as a patch to rb.