may be worth thinking about more flexible and beautiful
ways to display information... 'monitor', 'attach', etc,
along with termui, graphs...

output can be 'machiney'-- line-by-line,
or human-y -- pictures of buffalo and whatnot.

solution: use a go func connected to the node's Ethereum to grab and calculate relevant logs

rel ethereumproject#127
rel ethereumproject#318

---

TODO: fix or remove:
- downloading-from peers, eg 'this var/x/x peers'
- shows mode 'FullSync' before downloader initializes, even if it will be 'FastSync'

solution: comment code and include small explanation

solution: remove exploratory code that is not useless

solution: move to Warn from Error

solution: update it and simplify

solution:
- remove dead code, old notes
- remove units from --log-pace= argument, just use seconds as value (simpler is better)
- if mining, show STATUS MINE with minerthreads and hashrate (TODO: more?)
- gofmt

Rel ethereumproject#127, ethereumproject#318

solution: improve legibility

solution: relegate to debug

solution: share chan in main between shutdown and closing status log goroutine

solution: implement and glog SetAlsoToStdErr exported function and use in case of --log-dir

results in missing any logs after shutdown processes in FS logs

solution: defer log Flush after shutdown services

also decrease flushInterval from 30 -> 5 seconds (rate at which log buffer is written to FS)

solution: rename flag and flagvar and status log function

also adds logstatus flag to correct category for usage output

solution: refactor to use '--log-status='sync=60'' syntax, which can eventually support other features besides 'sync',
eg. mine, net, disk

…to cmd.go

solution: cut and paste and update imports

solution: error if neither fastblock nor fullblock match desired head number

fixes ethereumproject#325

solution: don't share os-interrupt channel as a global.
Notify library documentation clearly says Notify events can be called
multiple times and notification will be copied, so there's no harm in
listening for the same event on mutliple channels.

This pattern avoids a global and encourages per-feature handling of
shutdown scenarios.

…g-pace' wording

solution: fix