File

spec/scansion/version.scs @ 13651:b9d369f77121

prosodyctl: Further deprecate start/stop/restart commands when installed Despite the warning we introduced, many people continue to try using prosodyctl to manage Prosody in the presence of systemctl (e.g. #1688). Also, despite the warning, prosodyctl proceeded with the operation. This means the commands could be invoked by accident, and cause a situation that is hard to recover from (needing to manually track down stray processes). This commit disables all the problematic commands by default, but this can still be overridden using --force or via a config option. We only perform this check when we believe Prosody has been "installed" for system-wide use (i.e. running it from a source directory is still supported).
author Matthew Wild <mwild1@gmail.com>
date Thu, 06 Feb 2025 14:51:31 +0000
parent 10729:dbce2b94a7eb
line wrap: on
line source

# XEP-0092: Software Version / mod_version

[Client] Romeo
	password: password
	jid: romeo@localhost/dfaZpuxV

-----

Romeo connects

Romeo sends:
	<iq id='lx2' to='localhost' type='get'>
		<query xmlns='jabber:iq:version'/>
	</iq>

# Version string would vary so we can't do an exact match atm
# Inclusion of <os/> is disabled in the config, it should be absent
Romeo receives:
	<iq id='lx2' from='localhost' type='result'>
		<query xmlns='jabber:iq:version' scansion:strict='true'>
			<name>Prosody</name>
			<version scansion:strict='false'/>
		</query>
	</iq>


Romeo disconnects