X-Git-Url: https://git.pterodactylus.net/?a=blobdiff_plain;f=readme.txt;h=4ac04fc9677194dd0d115dbebc0905353a165144;hb=a558b16c8034966d14e1d63db44dcb952d849618;hp=038bb56f4adee381dff77035316dece4c7f431bd;hpb=9b22dd53fe62e312c1647310b7ec43aa127090af;p=fms.git

diff --git a/readme.txt b/readme.txt
index 038bb56..4ac04fc 100644
--- a/readme.txt
+++ b/readme.txt
@@ -1,7 +1,7 @@
 COMPILING
 ---------
-Compiling FMS requires CMake, pthreads and iconv if you want to do charset
-conversion.  Other required libraries are bundled with FMS.
+Compiling FMS requires CMake, Poco ( version >=1.2.9 ) and iconv if you want to
+do charset conversion.  Other required libraries are bundled with FMS.
 
 To compile, run these commands from the source directory:
 cmake -D I_HAVE_READ_THE_README=ON .
@@ -30,9 +30,26 @@ sure the user that runs FMS has read/write access to this directory.
 
 RUNNING
 -------
-You may run FMS in console mode by running the binary directly.  If you are
-running *nix and would like to run as a daemon, use the -d argument.  On
-Windows, -i will install FMS as a service, and -u will uninstall the service.
+You may run FMS in console mode by running the binary directly.  You can view
+available command line options by typing /help on Windows and --help on other
+platforms.  If you are running *nix and would like to run as a daemon, use the 
+--daemon argument.  On Windows, /registerService will install FMS as a service,
+and /unregisterService will uninstall the service.  Use the /displayName=name
+argument when installing the service to set the service name to whatever you
+want.  You will need to manually start the service unless you change the
+startup type in the service properties.
+
+If you are experiencing a problem with FMS that you can't solve, and you've
+already rebooted your machine, restarted FMS, and have reproduced the problem
+with a brand new database, follow these instructions.  Set the logging option
+to trace and restart FMS.  Create a post on the fms group with a descriptive
+subject and a body that contains the operating system you are using, along with
+a description of the problem, what you have tried already, if you are using a
+precompiled binary, the startup lines from the log file as well as the portion
+that corresponds to the problem you are experiencing, and any other information
+you have that pertains to the problem.  Make sure to anonymize any IP addresses,
+host names, subnet masks, and keys from the log that you don't want people to
+know about.
 
 EXITING
 -------