util.signal: Add support for signalfd(2) on Linux
signalfd allows handling signal events using the same method as sockets,
via file descriptors. Thus all signal dispatch can go through the same
main event loop as everything else, removing need for thread-scary
signal handling where execution would just jump to the signal handler
regardless of the state of Lua, and needing to keep track of Lua
states/threads.
-- Prosody IM
-- Copyright (C) 2008-2010 Matthew Wild
-- Copyright (C) 2008-2010 Waqas Hussain
--
-- This project is MIT/X11 licensed. Please see the
-- COPYING file in the source package for more information.
--
local st = require "prosody.util.stanza";
module:add_feature("jabber:iq:version");
local query = st.stanza("query", {xmlns = "jabber:iq:version"})
:text_tag("name", "Prosody")
:text_tag("version", prosody.version);
if not module:get_option_boolean("hide_os_type") then
local platform;
if os.getenv("WINDIR") then
platform = "Windows";
else
local os_version_command = module:get_option_string("os_version_command");
local ok, pposix = pcall(require, "prosody.util.pposix");
if not os_version_command and (ok and pposix and pposix.uname) then
platform = pposix.uname().sysname;
end
if not platform then
local uname = io.popen(os_version_command or "uname");
if uname then
platform = uname:read("*a");
end
uname:close();
end
end
if platform then
platform = platform:match("^%s*(.-)%s*$") or platform;
query:text_tag("os", platform);
end
end
module:hook("iq-get/host/jabber:iq:version:query", function(event)
local origin, stanza = event.origin, event.stanza;
origin.send(st.reply(stanza):add_child(query));
return true;
end);