toxcore/other/bootstrap_daemon
2014-08-16 23:19:23 -04:00
..
conf Renamed tox_bootstrap_daemon into tox-bootstrapd 2014-08-16 23:19:23 -04:00
Makefile.inc Renamed tox_bootstrap_daemon into tox-bootstrapd 2014-08-16 23:19:23 -04:00
README.md Renamed tox_bootstrap_daemon into tox-bootstrapd 2014-08-16 23:19:23 -04:00
tox-bootstrapd.c Renamed tox_bootstrap_daemon into tox-bootstrapd 2014-08-16 23:19:23 -04:00
tox-bootstrapd.sh Renamed tox_bootstrap_daemon into tox-bootstrapd 2014-08-16 23:19:23 -04:00

##Instructions for Debian

The following commands are to be executed as root:

  1. In tox-bootstrapd.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-bootstrapd.sh

  2. Execute:

mv tox-bootstrapd.sh /etc/init.d/tox-bootstrapd

(note that we removed .sh ending)

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

--

You can see daemon's log with

grep "tox-bootstrapd" /var/log/syslog

Note that system log is where you find your public key

--

###Troubleshooting:

  1. Check the log for errors with
grep "tox-bootstrapd" /var/log/syslog
  1. Check that paths in the beginning of /etc/init.d/tox-bootstrapd are valid

  2. Make sure that PIDFILE from /etc/init.d/tox-bootstrapd 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