Skip to content

Specify RPL_TIME #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 14, 2022
Merged

Specify RPL_TIME #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions _includes/modern-appendix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -668,6 +668,17 @@ Sent to a client which has just successfully issued an {% message OPER %} comman

Sent to an [operator](#operators) which has just successfully issued a {% message REHASH %} command. The text used in the last param of this message may vary.

{% numericheader RPL_TIME %}

"<client> <server> [<timestamp> [<TS offset>]] :<human-readable time>"

Reply to the {% message TIME %} command. Typically only contains the human-readable time, but it may include a UNIX timestamp.

Clients SHOULD NOT parse the human-readable time.

`<TS offset>` is used by some servers using a TS-based server-to-server protocol (eg. TS6), and represents the offset between the server's system time, and the TS of the network. A positive value means the server is lagging behind the TS of the network.
Clients SHOULD ignore its value.

{% numericheader ERR_UNKNOWNERROR %}

"<client> <command>{ <subcommand>} :<info>"
Expand Down