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
4c12ee3e30
toxcore/other/bootstrap_daemon
History
Tux3 / Mlkj / !Lev.uXFMLA 4c12ee3e30 Fix scope, ressource leaks in boostrap daemon 
Reduce scope of config_setting_t *elem

Fix various leaks of files keys_file and pid_file
2014-06-18 23:38:38 +02:00
..
conf Made config file more consistent with default values 2014-05-18 21:04:42 -04:00
Makefile.inc Install tox_bootstrap_daemon 2014-05-20 18:57:20 -07:00
README.md Renamed dht server to dht node 2014-02-22 17:07:15 -05:00
tox_bootstrap_daemon.c Fix scope, ressource leaks in boostrap daemon 2014-06-18 23:38:38 +02:00
tox_bootstrap_daemon.sh Made config file more consistent with default values 2014-05-18 21:04:42 -04:00

README.md

##Instructions for Debian

The following commands are to be executed as root:

  1. In tox_bootstrap_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_bootstrap_daemon.sh

  2. Execute:

mv tox_bootstrap_daemon.sh /etc/init.d/tox_bootstrap_daemon

(note that we removed .sh ending)

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

--

You can see daemon's log with

grep "tox_bootstrap_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_bootstrap_daemon" /var/log/syslog

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

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