StarMirror/toxcore
1
0
Fork 0
mirror of https://github.com/irungentoo/toxcore.git synced 2024-03-22 13:30:51 +08:00
Code Issues Projects Releases Wiki Activity
b9ef9b91af
toxcore/other/bootstrap_serverdaemon
History
Maxim Biro b9ef9b91af Added more error checking
2014-01-25 20:00:34 -05:00
..
conf Spellchecked everything 2014-01-19 14:14:25 -05:00
Makefile.inc Added .sh to the script 2014-01-19 17:21:24 -05:00
README.md Added .sh to the script 2014-01-19 17:21:24 -05:00
tox_dht_bootstrap_server_daemon.c Added more error checking 2014-01-25 20:00:34 -05:00
tox_dht_bootstrap_server_daemon.sh Added .sh to the script 2014-01-19 17:21:24 -05:00

README.md

##Instructions for Debian

The following commands are to be executed as root:

  1. In tox_dht_bootstrap_server_daemon.sh file change:
  • CFG to where your config file (conf) will be; read rights required
  • DAEMON to point to the executable
  • PIDFILE to point to a pid file daemon would have rights to create

  1. Go over everything in conf. Make sure pid_file_path matches PIDFILE from tox_dht_bootstrap_server_daemon.sh

  2. Execute:

mv tox_dht_bootstrap_server_daemon.sh /etc/init.d/tox_dht_bootstrap_server_daemon

(note that we removed .sh ending)

  1. Give the right permissions to this file:
chmod 755 /etc/init.d/tox_dht_bootstrap_server_daemon
  1. Execute:
update-rc.d tox_dht_bootstrap_server_daemon defaults
  1. Start the service:
service tox_dht_bootstrap_server_daemon start
  1. Verify that the service is running:
service tox_dht_bootstrap_server_daemon status

--

You can see daemon's log with

grep "tox_dht_bootstrap_server_daemon" /var/log/syslog

Note that system log is where you find your public key

--

###Troubleshooting:

  1. Check the log for errors with
grep "tox_dht_bootstrap_server_daemon" /var/log/syslog

  1. Check that paths in the beginning of /etc/init.d/tox_dht_bootstrap_server_daemon are valid

  2. Make sure that PIDFILE from /etc/init.d/tox_dht_bootstrap_server_daemon matches with the pid_file_path from conf

  3. Make sure you have write permission to keys and pid files

  4. Make sure you have read permission for config file