Cleanup docs formatting
Fix indents of some pages, the wrong indent let to gray bars besides them. Also, fix a typo and add some markup. Change-Id: I6e7126ef7b782b376efcc7c6d69c6de9a504ddb5
This commit is contained in:
parent
dde24421d0
commit
1c6b4876eb
@ -278,17 +278,17 @@ commands which may be required for channel operators.
|
||||
Operator status is sometimes required to perform certain commands in your
|
||||
channel (though most everything can be done through `/msg chanserv` commands
|
||||
instead if permission flags are set correctly). To give yourself operator
|
||||
status in a channel, use the following command:
|
||||
status in a channel, use the following command::
|
||||
|
||||
/msg chanserv op #channel
|
||||
|
||||
You don't need to become an operator to change the topic, this can be done
|
||||
via Chanserv:
|
||||
via Chanserv::
|
||||
|
||||
/msg chanserv topic #channel New topic goes here.
|
||||
|
||||
If you are curious as to who has access to a channel, you can issue this
|
||||
command:
|
||||
command::
|
||||
|
||||
/msg chanserv access #channel list
|
||||
|
||||
@ -360,22 +360,24 @@ Troubleshooting
|
||||
|
||||
Bots may stop responding, common steps to troubleshoot the problem are:
|
||||
|
||||
1. Check status of the bot, with:
|
||||
1. Check status of the bot, with::
|
||||
|
||||
service xxxbot status
|
||||
|
||||
If bot is stopped, start it again. Restart the bot if you see it's running
|
||||
but not operating properly.
|
||||
If the bot is stopped, start it again. Restart the bot if you see
|
||||
it's running but not operating properly.
|
||||
|
||||
2. On bot restart, it may show problems connecting to chat.freenode.net.
|
||||
If bot logs show it's stopped on connection, you can manually try with:
|
||||
If bot logs show it's stopped on connection, you can manually try
|
||||
with::
|
||||
|
||||
telnet chat.freenode.net 6667
|
||||
|
||||
3. For bots on the eavesdrop server: if you don't have connection to that
|
||||
port, check entries on /etc/hosts for chat.freenode.net, until you find one
|
||||
server that is operative. Switch the entries on /etc/hosts to choose
|
||||
the right one, and restart the service with:
|
||||
3. For bots on the eavesdrop server: if you don't have connection to
|
||||
that port, check entries on ``/etc/hosts`` for
|
||||
``chat.freenode.net``, until you find one server that is operative.
|
||||
Switch the entries on ``/etc/hosts`` to choose the right one, and
|
||||
restart the service with::
|
||||
|
||||
sudo service xxxbot restart
|
||||
|
||||
|
@ -61,7 +61,7 @@ And if you have any questions, please ask.
|
||||
Bugs
|
||||
====
|
||||
|
||||
The infrastructure project maintains a bug list at:
|
||||
The infrastructure project maintains a bug list at::
|
||||
|
||||
https://storyboard.openstack.org/#!/project_group/55
|
||||
|
||||
|
@ -278,7 +278,7 @@ should configure as follows::
|
||||
To format the result's message in a way that works with the current OpenStack
|
||||
Gerrit GUI parser, configure the ``URL to post`` parameter (under the
|
||||
``Gerrit Reporting Values`` section) for each job. The correct value for this
|
||||
paramater is:
|
||||
parameter is::
|
||||
|
||||
\* $JOB_NAME $BUILD_URL
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user