(https://bugs.launchpad.net/tarantool/+bug/1169200)

No test case since the bug only manifsets itself under
concurrent load.

With addition of on_disconnect triggers, iproto_session_destroy()
was invoked from two places: the request handler code and
iproto_session_disconnect callback.

This could destroy the same session twice. Worse yet, it would
be put to the session cache twice, as a free session, and then
used twice for two different client sockets.

This could end up in an unpredictable mess, best case: libev
event loop runs infinitely since libev fd has events, while
session->input.fd is already set to -1 any attempt to use the
session ends up with an exception. At the same time the session
in this condition can not be destroyed since it's impossible to
tell libev forget about a file descriptor about which we already
know nothing.

A fix and a test case for Bug#1075677
"incorrect conversion from boolean lua value to tarantool tuple".

Support boolean in conversion.

Replication relay was created (forked) after initialization
of slab allocator, and, consequently, had a very large address
space. The memory wasn't used really.

Initialize slab allocator after creation of a replication
relay process.

No test case since we don't have automation to detect that sort
of problems.

Review comments.

Conflicts:
	include/fiber.h

Remove added logging, a message with 'saving snapshot %filename'
is already printed to the log by the child. It contains
snapshot pid. Snapshot fid is not as useful once the bug
is fixed.

https://bugs.launchpad.net/tarantool/+bug/1162797

by SIGUSR1 tarantool
- didn't touch box.info.snapshot_pid
- didn't waitpid for snapshot process

Conflicts:

	include/fiber.h

(https://bugs.launchpad.net/tarantool/+bug/1160869)

flag is set.
(https://bugs.launchpad.net/tarantool/+bug/1160877)

getaddrinfo("::1") may fail if machine has no public ipv6 addresses due
to AI_ADDRCONFIG behaviour.

(https://bugs.launchpad.net/tarantool/+bug/1160869)

Lua socket object creates coio object that bind to a current
fiber, after yield it will resume it in a different fiber
context after a complete io operation.

Fix this situation by updating current coio fiber in most
lua socket operations.

https://bugs.launchpad.net/tarantool/+bug/1160789

When multiple sessions get disconnected at the same
time, the same fiber is running all disconnect triggers.
This fiber's sid was  not changed between trigger invocations,
and on_disconnect() triggrer of the next disconnected
session would see not its own session id in box.session.id(),
but the previous session's session id.

The fix is to correctly set box.session.id() before handling
any iproto request.
In on_connect() request, sid is 0, but soon it is
reset in session_create().

No test case since the bug requires that there is a full
libev queue, so that multiple on_disconnect() triggers
fire in the same loop.