Skip to content

Commit 9d1efd5

Browse files
committed
Change init.d to SysVinit
1 parent 516d5ac commit 9d1efd5

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

other/bootstrap_daemon/README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,18 @@
55
- [Updating](#systemd-updating)
66
- [Troubleshooting](#systemd-troubleshooting)
77
<br>
8-
- [For `init.d` users](#initd)
9-
- [Setting up](#initd-setting-up)
10-
- [Updating](#initd-updating)
11-
- [Troubleshooting](#initd-troubleshooting)
8+
- [For `SysVinit` users](#sysvinit)
9+
- [Setting up](#sysvinit-setting-up)
10+
- [Updating](#sysvinit-updating)
11+
- [Troubleshooting](#sysvinit-troubleshooting)
1212
<br>
1313
- [For `Docker` users](#docker)
1414
- [Setting up](#docker-setting-up)
1515
- [Updating](#docker-updating)
1616
- [Troubleshooting](#docker-troubleshooting)
1717

1818

19-
These instructions are primarily tested on Debian Linux, Wheezy for init.d and Jessie for systemd, but they should work on other POSIX-compliant systems too.
19+
These instructions are primarily tested on Debian Linux, Wheezy for SysVinit and Jessie for systemd, but they should work on other POSIX-compliant systems too.
2020

2121

2222
<a name="systemd" />
@@ -115,10 +115,10 @@ sudo journalctl -f _SYSTEMD_UNIT=tox-bootstrapd.service
115115
- Make sure tox-bootstrapd location matches its path in tox-bootstrapd.service file.
116116

117117

118-
<a name="initd" />
119-
##For `init.d` users
118+
<a name="sysvinit" />
119+
##For `SysVinit` users
120120

121-
<a name="initd-setting-up" />
121+
<a name="sysvinit-setting-up" />
122122
###Setting up
123123

124124
For security reasons we run the daemon under its own user.
@@ -164,7 +164,7 @@ Get your public key and check that the daemon initialized correctly:
164164
sudo grep "tox-bootstrapd" /var/log/syslog
165165
```
166166

167-
<a name="initd-updating" />
167+
<a name="sysvinit-updating" />
168168
###Updating
169169

170170
You want to make sure that the daemon uses the newest toxcore, as there might have been some changes done to the DHT, so it's advised to update the daemon at least once every month.
@@ -185,7 +185,7 @@ After all of this is done, simply start the daemon back again:
185185
sudo service tox-bootstrapd start
186186
```
187187

188-
<a name="initd-troubleshooting" />
188+
<a name="sysvinit-troubleshooting" />
189189
###Troubleshooting
190190

191191
- Check daemon's status:

0 commit comments

Comments
 (0)