Since there isn't neutral ground, on the rtmp state callback we actually have to force the write lock of the session, but we only need a try lock on removing the session from the rsession->session_hash. This removes a deadlock caused when we had to enforce with locks that the rsession couldn't be destroyed if the FS session was in the middle of a hangup.

Seems having a read lock still prevents a write lock to be taken, even if the thread that is trying to get the write lock currently has the read lock.

Fixes -Wl,-z,now / -Wl,-z,defs errors about undefined symbols.
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Making the build -Wl,--as-needed safe.
Tested on Centos 5.x + Gentoo.
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Full clang error message:

  error: implicit conversion from enumeration type 'ftdm_bool_t' to
  different enumeration type 'ftdm_status_t' [-Werror,-Wconversion]
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Fixes "warning: comparison of unsigned expression >= 0 is always true".
Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

Signed-off-by: Stefan Knoblich <stkn@openisdn.net>

after 25 hours. I guess not many people are inserting header lines on FAX pages.
Hopefully this update fixes the problem.

FS-5325 i'll put the nonblocking in but I still think this is a problem with openssl, a short read is not there every single time you connect, When the lib is in full blocking mode it should be handling the complicated actions internally.  As complicated as socket programming is, async ssl is even worse because it requires you to do your own buffering and attemps to read may fail waiting for you to write or vice-versa which should have been handled for us in the lib.  non-interruptable syscalls are getting pretty outdated and not enabling it is much less complex than making every socket app on earth be non-blocking