source: code/trunk/doc/suika.1@ 822

Last change on this file since 822 was 817, checked in by yakumo.izuru, 2 years ago

See you in Hell, scdoc!

Signed-off-by: Izuru Yakumo <yakumo.izuru@…>

File size: 2.8 KB
Line 
1.Dd $Mdocdate$
2.Dt SUIKA 1
3.Os
4.Sh NAME
5.Nm suika
6.Nd Drunk as hell IRC bouncer oni.
7.Sh SYNOPSIS
8.Nm
9.Op Fl options
10.Ar ...
11.Sh DESCRIPTION
12suika is an user-friendly IRC bouncer.
13It connects to upstream IRC servers on
14behalf of the user to provide extra
15features.
16
17.Bl -tag -width 10n -compact
18.It *
19Multiple separate users sharing the same
20bouncer, each with their own upstream
21servers
22.It *
23Clients connecting to multiple upstream
24servers via a single connection to the
25bouncer
26.It *
27Sending the backlog (messages received
28while the user was disconnected from
29the bouncer), with per-client buffers
30.El
31
32When joining a channel, the channel will
33be saved and automatically joined on
34the next connection. When registering
35or authenticating with NickServ, the
36credentials will be saved and
37automatically used on the next
38connection if the server supports
39SASL. When parting a channel with
40the reason "detach", the channel
41will be detached instead of being
42left.
43
44When all clients are disconnected
45from the bouncer, the user is
46automatically marked as away.
47
48suika supports two connection modes:
49
50.Bl -tag -width 10n -compact
51.It Single upstream mode
52one downstream connection maps to one upstream
53connection. To enable this mode,
54connect to the bouncer with the username
55"<username>/<network>".
56If the bouncer isn't connected to the upstream
57server, it will get automatically added.
58Then channels can be joined and
59parted as if you were directly
60connected to the upstream server.
61.It Multiple upstream mode
62one downstream connection maps to multiple upstream
63connections.
64Channels and nicks are suffixed
65with the network name. To join
66a channel, you need to use
67the suffix too:
68/join #channel/network.
69Same applies to messages
70sent to users.
71.El
72
73For per-client history to work, clients need to indicate their name. This can
74be done by adding a "@<client>" suffix to the username.
75
76suika will reload the configuration file, the TLS certificate/key and the MOTD
77file when it receives the HUP signal. The configuration options listen, db
78and log cannot be reloaded.
79
80Administrators can broadcast a message to all bouncer users via /notice
81$<hostname> <text>, or via /notice $\* <text> in multi-upstream mode. All
82currently connected bouncer users will receive the message from the special
83BouncerServ service.
84
85.Sh OPTIONS
86.Bl -tag -width 11n -compact
87.It -h, -help
88Show help message and quit
89.It -config <path>
90Path to the config file. If unset, a default config file is used.
91.It -debug
92Enable debug logging (this will leak sensitive information
93such as passwords)
94.It -listen <uri>
95Listening URI (default ":6697"). Can be specified multiple times.
96.El
97.Sh SEE ALSO
98.Xr suika-config 5
99.Xr suika-bouncerserv 7
100.Sh AUTHORS
101.An Simon Ser and contributors https://emersion.fr
102.An Izuru Yakumo Aq Mt yakumo.izuru@chaotic.ninja
Note: See TracBrowser for help on using the repository browser.