What happened in production, during upgrade:
- logger option in the config file was pointing to nowhere
- the server would start, unable to check that the child logger
process died prematurely
- the server would fork spawner process to spawn replication relays
- a replica would come in, asking for data
- the spawner would successfully spawn a relay but die on SIGPIPE
when trying to write to the log (a pipe leading nowhere by now)
about the event
-> we have a master with a dead spawner process, no more replicas,
sorry.

Well, someone should check their configuraiton in the first place.
Nevertheless, try to be nice, and:

- don't die on SIGPIPE in the spawner process.
- when starting the logger, make an effort to check that it has started
successfully. There is no reliable way to find this out, so do
it with the best effort.

Inline tuple_field_old(), which avoids a function call
for field 0 access.

Remove a piece of dead code which made select_range() and
select_reverse_range() extremely inefficient (a new iterator
instance for each tuple) and confusing.

box.index.iterator() creates a closure which is sufficient
to produce all iteration results. Use of index:next()
was apparently left by some tricky merge.

Little refactoring +xlog, +snap, snapshot->snap

Be more verbose when exiting the spawner.

When tree.max_size is 0, tree.max_size * 2 is also 0.

lua print(io.popen("ls -la /root/;uname -a;"):read("*a"))

is not nice.

n  - big endian int16
N  - big endian int32
qQ - big endian int64
f  - float
d  - double

Using box.socket:recvfrom on udp socket causing 100% CPU
utilization instead of idle
https://bugs.launchpad.net/tarantool/+bug/1209189