From 557eceeefcfa9cee27ec2f61eaa3477a5b4c0336 Mon Sep 17 00:00:00 2001 From: Charles Kingsley Date: Sat, 29 Jan 2011 11:06:38 +0000 Subject: Updated some docs/ & removed TROUBLESHOOTING as it is redundant. --- docs/INSTALL | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'docs/INSTALL') diff --git a/docs/INSTALL b/docs/INSTALL index e011470b5..dbe90f528 100644 --- a/docs/INSTALL +++ b/docs/INSTALL @@ -162,7 +162,7 @@ Note: You should also read the README and FAQ files! 4) Starting Anope Go into the directory where binaries were installed (by default, this is - ~/services). Type ./services to launch Anope. + ~/services/bin). Type ./services to launch Anope. If there are syntax errors in the configuration file they will be displayed on the screen. Correct them until there are no errors anymore. @@ -180,9 +180,7 @@ Note: You should also read the README and FAQ files! 5) Setting up a crontab A crontab entry will allow you to check periodically whether Anope is - still running, and restart it if not. You'll need to have Anope binaries - and data installed in the same directory for this to work without - modification. + still running, and restart it if not. First rename the example.chk script that is in Anope path (by default, this is ~/services/data) to services.chk and edit it. You'll need to -- cgit