| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
prosody.shutdown() relies on prosody.main_thread, which has not been set
yet at this point.
Doing a clean shutdown might actually be harmful in case it tears down
things set up by the conflicting Prosody, such as the very pidfile we
were looking at.
Thanks again SigmaTel71 for noticing
|
| |\ |
|
| | |
| |
| |
| |
| | |
This ensures that domain names of virtual hosts and components are valid in
XMPP, and that they are encoded correctly.
|
| | |
| |
| |
| |
| | |
Prevents creation of log files owned by the root user which could be
inaccessible once started correctly.
|
| | |
| |
| |
| | |
root (thanks SigmaTel71)
|
| | |
| |
| |
| |
| |
| |
| |
| | |
SigmaTel71)
Ensures that startup.detect_platform() runs so know whether to use the
POSIX method of checking the current user or something else. Also after
reading the config so we know whether the root override setting is set.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows greater control over the order of events.
Notably, the internal ordering between daemonization, initialization of
libunbound and setup of signal handling is sensitive.
libunbound starts a separate thread for processing DNS requests.
If this thread is started before signal handling has been set up, it
will not inherit the signal handlers and instead behave as it would have
before signal handlers were set up, i.e. cause the whole process to
immediately exit.
libunbound is usually initialized on the first DNS request, usually
triggered by an outgoing s2s connection attempt.
If daemonization happens before signals have been set up, signals may
not be processed at all.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Broke signal handling again, such that an early s2s connection results
in libunbound catching signals and getting Prosody killed on e.g. SIGHUP
This returns to the situation where prosody --daemonize does not respond
to signals.
|
| | |
| |
| |
| |
| |
| | |
signalfds stop working with epoll after forking
hooking signals later should not affect anything
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | | |
|
| | |
| |
| |
| | |
100,000 iterations of match() on my laptop from 3.5s -> 0.5s.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
It was mainly used to determine whether to try IPv6 or IPv4 first,
following the rules for this in the RFC.
Now we always try IPv6 and IPv4 at roughly the same time, thus there no
need to carry these rules.
|
| | |
| |
| |
| | |
for convenience.
|
| | | |
|
| | |
| |
| |
| |
| | |
e.g.
prosodyctl shell muc room room@muc.example.com :set_name "This Room"
|
| | |
| |
| |
| |
| |
| | |
whitespace
Seen in some other template languages
|
| | | |
|
| | |
| |
| |
| | |
Thanks MattJ
|
| | |
| |
| |
| |
| | |
The new method parse_duration_lax() exports the old behaviour, mainly for
compatibility purposes.
|
| | |
| |
| |
| | |
Should get rid of fseek() call
|
| | |
| |
| |
| | |
Maybe we need some sort of lint for this?
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is purely for informational purposes, so it's possible to determine
externally whether a runner is using the default runner function (which
executes functions as work items) or a custom runner function.
|
| | |
| |
| |
| | |
Mostly expected to be useful for debugging purposes.
|
| | |
| |
| |
| | |
Knowing the state of the coroutine as well as the runner state can be helpful.
|
| | |
| |
| |
| | |
This can be used for debugging and introspection.
|
| | |
| |
| |
| |
| | |
This would indicate that a reverse proxy is used, which gets to be
responsible for that since it probably holds the actual cert.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The 'anonymous_login' setting is deprecated and prosodyctl check config
will tell you to change it to 'authentication = "internal_hashed"', so
we shouldn't need to care about here anymore.
|
| | |
| |
| |
| | |
This code is hard to follow and in need of some refactoring.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Allows sorting by id as a substitute for sorting by timestamp since it
has the timestamp in the encoded in the first part, and only things that
happen extremely close together may get out of order by such a sort,
which might not matter.
From draft-ietf-uuidrev-rfc4122bis formerly draft-peabody-dispatch-new-uuid-format
|
| | |
| |
| |
| | |
modules_enabled (thanks aab and Menel)
|
| | | |
|
| | |
| |
| |
| | |
Not the prosodyctl check dane I wanted to make but a start.
|
| | |
| |
| |
| |
| |
| |
| | |
One small refactor but one huge step in the right direction
Mostly because adding another check would make the line checking for a
valid check exceed the column limit.
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| | |
The code would have suggested adding to modules_enabled instead of
modules_disabled
|
| | |
| |
| |
| | |
Backport of ffe4adbd2af9 since new was added in the 0.12 branch
|
| | | |
|
| | |
| |
| |
| | |
According to MattJ, leftovers from an earlier vision for util.sql
|
| | |
| |
| |
| |
| | |
Many leftovers from the earlier version of util.sql this was based on
and cleanup applied there since then.
|
| | |
| |
| |
| |
| |
| | |
Shifting the index does not work reliably yet, better to rebuild it from
scratch. Since there is minimal parsing involved in that, it should be
more efficient anyway.
|
| | | |
|
| | |
| |
| |
| |
| | |
It gets closed eventually but at high load they could potentially
lead to reaching FD limits faster.
|
| | |
| |
| |
| | |
In desperate need of tests
|
| | |
| |
| |
| |
| | |
Until we have more test coverage. Somehow the index becomes incorrect
after inserting padding, unclear why.
|
| |\| |
|
