#287 Allow interacting with the server on stdin/stdout
For diagnostics, monitoring, and autonomous server control, it would be useful to be able to interact with the server via stdin/stdout. A possibility: treat stdin/stdout like a dm-level commandline, and allow a subset of DM commands and their responses. The most useful commands would include:
time
arrest
banish
debug
dump (several variants)
freeze
kick
malloc
plugin
pluglist
plugout
recollect
reset
server_speed
settings
shutdown <- This would be particularly useful for one of my projects
Some other idle ideas:
Using the chat or shout commands on stdin would also be neat, which lets the admin send scripted messages, carry on a conversation, or even bridge or log the chat elsewhere.
It might be a bit more complex, but perhaps the server could support several named pipes, and put/listen various types of messages on each one. For example:
Pipes dedicated to the global shout and chat messages make bridging the chat into IRC or other systems much easier.
Pipes for dump or debug info allow dumping info without cluttering the primary copy of stdout.
Separating ad-hoc commands and their responses from regular logs makes it easier for an admin to interact with the server without being constantly interrupted.
