scripts in server bin directory issues

Here is a list of what I found out looking at most of the the scripts:

classpath.sh:

• relative classpath is generated like "somepath/../something:somepath0/../something0:..." (".." is just lame here)
• as well doesn't have a windows batch equivalent

twiddle.bat/sh:

• Autodiscovery is still active if server url is specified so result is unreliable (for example may return result from another running server if what we try to query is dead)
• doesn't support HttpNamingContextFactory (that's minor, it was included in shutdown in 5.x)

shutdown:

• doesn't support HttpNamingContextFactory (that's minor, it was included in shutdown in 5.x)

jboss_init_*:

• redhat one is not touching a lock in /var/lock/subsys so I doubt "stop" will be invoked by Red Hat init system on shutdown
• doesn't wait for the server to start/stop but return to shell; server stopped is tested but script should wait for everything to complete rather than hope jboss will shutdown gracefully before the regular init process kill it (i.e. server will die with the init system sending kill -9 rather through the standard mechanism)
• haven't looked at the suse and hp-ux ones due to lack of time
• why not move these to some dir for example contrib? To show that it is not guaranteed to work. I'm working on a security lock-up script that is also good to go in there.

probe.sh - doesn't exit with a non-null status when nothing is found (intentional?)