mod_posix: Move POSIX signal handling into util.startup to avoid race When libunbound is initialized, it spawns a thread to work in. In case a module initializes libunbound, e.g. by triggering a s2s connection, Prosody would not handle signals, instead immediately quit on e.g. the reload (SIGHUP) signal. Likely because the libunbound thread would not have inherited the signal mask from the main Prosody thread. Thanks Menel, riau and franck-x for reporting and help narrowing down

     1

     2

local random = require "util.random";

     3

     4

describe("util.random", function()

     5

	describe("#bytes()", function()

     6

		it("should return a string", function()

     7

			assert.is_string(random.bytes(16));

     8

		end);

     9

    10

		it("should return the requested number of bytes", function()

    11

			-- Makes no attempt at testing how random the bytes are,

    12

			-- just that it returns the number of bytes requested

    13

    14

			for i = 1, 20 do

    15

				assert.are.equal(2^i, #random.bytes(2^i));

    16

			end

    17

		end);

    18

	end);

    19

end);