mirror of
https://github.com/ChronosX88/psyced.git
synced 2024-11-08 19:41:00 +00:00
people, don't use debug levels over 1!
This commit is contained in:
parent
821fb55b20
commit
72815ca429
230
INSTALL.txt
230
INSTALL.txt
@ -1,9 +1,8 @@
|
|||||||
|
Installing the psyced
|
||||||
Installing the psycMUVE
|
|
||||||
|
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
We're very proud to see you are about to install a psycMUVE!
|
We're very proud to see you are about to install a psyced!
|
||||||
|
|
||||||
(Windows System)
|
(Windows System)
|
||||||
You received this in form of an executable. By executing it you
|
You received this in form of an executable. By executing it you
|
||||||
@ -11,12 +10,17 @@ We're very proud to see you are about to install a psycMUVE!
|
|||||||
configuration interface. So essentially you don't need any help here.
|
configuration interface. So essentially you don't need any help here.
|
||||||
Please move directly on to the FIRSTSTEPS document once you have
|
Please move directly on to the FIRSTSTEPS document once you have
|
||||||
done the installation.
|
done the installation.
|
||||||
[1]http://muve.pages.de/FIRSTSTEPS
|
[1]http://www.psyced.org/FIRSTSTEPS
|
||||||
|
|
||||||
|
(Gentoo Linux System)
|
||||||
|
Download the ebuilds which are available from [2]http://www.psyced.org
|
||||||
|
and follow the instructions inside. Once psyced is emerged you can go
|
||||||
|
directly to chapter 3.
|
||||||
|
|
||||||
(Linux or Unix System)
|
(Linux or Unix System)
|
||||||
In a nutshell, all you have to do is execute './install.sh' and go from
|
In a nutshell, all you have to do is execute './install.sh' and go from
|
||||||
there. It will tell you to download an LDMUD driver from
|
there. It will tell you to download an LPC driver from
|
||||||
[2]http://muve.pages.de/ldmud
|
[3]http://lpc.psyc.eu
|
||||||
then compile and configure it with you interactively. So you don't need
|
then compile and configure it with you interactively. So you don't need
|
||||||
to know anything more now, but if you want more information, read on.
|
to know anything more now, but if you want more information, read on.
|
||||||
|
|
||||||
@ -27,43 +31,52 @@ We're very proud to see you are about to install a psycMUVE!
|
|||||||
something has gone wrong. Don't try to figure it out alone, talk to us.
|
something has gone wrong. Don't try to figure it out alone, talk to us.
|
||||||
And.. please be patient with our slow response times.
|
And.. please be patient with our slow response times.
|
||||||
|
|
||||||
psyc://ve.symlynX.com/@psyc
|
psyc://psyced.org/@welcome
|
||||||
[3]irc://ve.symlynX.com/psyc
|
[4]irc://psyced.org/#welcome
|
||||||
[4]telnet ve.symlynX.com
|
[5]http://psyced.org/PSYC/
|
||||||
/go psyc
|
[6]telnet psyced.org
|
||||||
[5]http://ve.symlynX.com:33333/PSYC/
|
|
||||||
|
|
||||||
|
|
||||||
0. System Requirements
|
0. System Requirements
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
You can skip this if you think you have a sanely configured unix system.
|
You can probably skip this if you think you have a sanely configured
|
||||||
|
GNU/POSIX system.
|
||||||
|
|
||||||
The following requirements exist for building psycMUVE and ldmud:
|
The following requirements exist for building psyced and psyclpc:
|
||||||
|
|
||||||
o Disk Space:
|
o Disk Space:
|
||||||
|
|
||||||
Make sure you have approximately 7 MB of temporary free disk space
|
Make sure you have approximately 7 MB of temporary free disk space
|
||||||
available. After installation psycMUVE occupies approximately 3 MB of
|
available. After installation psyced occupies approximately 3 MB of
|
||||||
disk space (the current required disk space depends on the amount of
|
disk space (the actual required disk space depends on the amount of
|
||||||
users, logs etc).
|
users, logs etc).
|
||||||
|
|
||||||
o ANSI-C Compiler:
|
o ANSI-C Compiler:
|
||||||
|
|
||||||
Make sure you have an ANSI-C compiler installed. The GNU C compiler
|
Make sure you have an ANSI-C compiler installed. The GNU C compiler
|
||||||
(GCC) from the Free Software Foundation (FSF) is recommended.
|
(GCC) from the Free Software Foundation (FSF) is recommended.
|
||||||
You can find the homepage of GNU at [6]http://www.gnu.org/. GCC
|
You can find the homepage of GNU at [7]http://www.gnu.org/. GCC
|
||||||
binaries for Solaris can be loaded from [7]http://www.sunfreeware.com/.
|
binaries for Solaris can be loaded from [8]http://www.sunfreeware.com/.
|
||||||
|
|
||||||
o POSIX YACC compliant grammar compiler
|
o POSIX YACC compliant grammar compiler
|
||||||
|
|
||||||
You probably have either bison or yacc installed, otherwise do the
|
You probably have either bison or yacc installed, otherwise do the
|
||||||
appropriate emerge or whatever software installation.
|
appropriate emerge or whatever software installation.
|
||||||
|
|
||||||
o Perl 5 Interpreter [OPTIONAL]
|
o Useful C libraries
|
||||||
|
|
||||||
|
OpenSSL, pcre, zlib, idn > 0.5.5, nsl, mlib.
|
||||||
|
|
||||||
|
o Some standard or popular Unix applications
|
||||||
|
|
||||||
|
bzip2, make, egrep, touch, uname, sh, sed, fileutils etc.
|
||||||
|
|
||||||
|
o PERL 5 Interpreter
|
||||||
|
|
||||||
The distribution includes some perl scripts that may or may not
|
The distribution includes some perl scripts that may or may not
|
||||||
be useful.
|
be useful. 'psyconf' in particular is needed to get the configuration
|
||||||
|
in place, it is however not needed at runtime.
|
||||||
|
|
||||||
|
|
||||||
1. How to compile an LPC driver manually
|
1. How to compile an LPC driver manually
|
||||||
@ -74,23 +87,25 @@ We're very proud to see you are about to install a psycMUVE!
|
|||||||
information for you to get it done right is lessened if you let the
|
information for you to get it done right is lessened if you let the
|
||||||
process do it.
|
process do it.
|
||||||
|
|
||||||
[8]http://lpc.pages.de will direct you to the current download areas for
|
[9]http://lpc.psyc.eu will direct you to the current download areas for
|
||||||
a PSYC-enabled LPC driver, like currently LDMUD. The LDMUD driver uses
|
the PSYC-enabled LPC driver, psyclpc. It uses
|
||||||
a standard autoconfiguration system which on most systems does all the
|
a standard auto-configuration system which on most platforms does all the
|
||||||
work for you (for exceptions see below). That's how install.sh can do it
|
work for you (see below for exceptions). That's how install.sh can do it
|
||||||
just like that.
|
just like that.
|
||||||
|
|
||||||
To prepare the compilation, enter the src directory of LDMUD and execute
|
To prepare the compilation, enter the src directory of the LPC driver and
|
||||||
the 'psycmuve' script located in '[9]world/drivers/ldmud/patches/psycmuve'.
|
execute './configure' (which will run the 'settings/psyced' script).
|
||||||
within the src/settings directory of LDMUD, or -even better- use
|
The default target directory is '/opt/psyced' or a subdirectory of your
|
||||||
the maybe more up to date 'psycmuve' file in the patches directory
|
home directory if you are installing in user mode. Please edit the
|
||||||
of world/drivers/ldmud. The default target directory is /opt/psycmuve -
|
'settings/psyced' script if you need a different path. You may want to
|
||||||
please edit the script if you need a different path.
|
tweak some compilation configuration settings contained in that file,
|
||||||
|
but there isn't a need to.
|
||||||
|
|
||||||
|
|
||||||
After configuration is finished, you may want to modify the Makefile
|
After configuration is finished, you may want to modify the Makefile
|
||||||
to fine tune those parameters which are not covered by the configuration.
|
to fine tune those parameters which are not covered by the configuration.
|
||||||
(like maybe change 'INSTALL=./install.sh -c' to 'INSTALL=./install.sh')
|
(like maybe change 'INSTALL=./install.sh -c' to 'INSTALL=./install.sh')
|
||||||
But there is generally no need to do anything really.
|
But there is generally no need to do anything.
|
||||||
|
|
||||||
The compilation is done using make. Following targets are implemented:
|
The compilation is done using make. Following targets are implemented:
|
||||||
|
|
||||||
@ -99,101 +114,148 @@ We're very proud to see you are about to install a psycMUVE!
|
|||||||
utils: compile the utilities, especially the ERQ daemon
|
utils: compile the utilities, especially the ERQ daemon
|
||||||
install-utils: compile and install the utilities in ${bindir}
|
install-utils: compile and install the utilities in ${bindir}
|
||||||
|
|
||||||
For more details feel free to read the LDMUD INSTALL file.
|
You will need an 'psyclpc' and an 'erq' binary for psyced to work.
|
||||||
|
For more details feel free to read the driver's INSTALL file.
|
||||||
|
|
||||||
|
|
||||||
2. Okay, let's install it!
|
2. Okay, let's install it!
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
To install psycMUVE, execute the './install.sh' script from within
|
To install psyced, execute the './install.sh' script from within
|
||||||
the distribution directory. On some systems you may have to use a
|
the distribution directory. On some systems you may have to use a
|
||||||
different shell, like 'ksh install.sh' or 'bash install.sh'.
|
different shell, like 'ksh install.sh' or 'bash install.sh'.
|
||||||
|
|
||||||
You will be asked some configuration questions. When done, it will
|
You will be asked some configuration questions. When done, it will
|
||||||
create several files for you and transfer the content of the psycMUVE
|
create several files for you and transfer the content of the psyced
|
||||||
distribution to the target directory you specified interactively.
|
distribution to the target directory you specified interactively.
|
||||||
Depending on your userid (root or other) you will be given
|
Depending on your userid (root or other) you will be given
|
||||||
/opt/psycmuve or ~/psycmuve as defaults for installation. We
|
/opt/psyced or ~/psyced as defaults for installation. We
|
||||||
continue this documentation assuming you picked the root defaults.
|
continue this documentation assuming you picked the root defaults.
|
||||||
|
|
||||||
Start psycMUVE:
|
Start psyced:
|
||||||
/opt/psycmuve/bin/psycmuve
|
/opt/psyced/bin/psyced
|
||||||
|
|
||||||
Test it:
|
Test it:
|
||||||
telnet localhost 2000
|
telnet localhost 2323
|
||||||
or
|
or
|
||||||
irc <nick> localhost
|
irc <nick> localhost
|
||||||
|
|
||||||
|
|
||||||
3. Configuring psycMUVE
|
3. Configuring psyced
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
We have a very very useful web-based configuration tool.
|
Either install.sh has generated a psyced.ini for you, or your
|
||||||
The installation process will direct you to it. If you want to
|
software management tools have produced one for you. It usually
|
||||||
activate it manually, edit local/local.h and add the following
|
resides in /etc/psyc, but you may have chosen to put it elsewhere.
|
||||||
line: '#define WEB_CONFIGURE' - As you restart the MUVE you will
|
|
||||||
be able to use it at [10]http://localhost:44444/net/http/configure
|
|
||||||
|
|
||||||
Careful who else may have access to the localhost address.
|
Have a look into that file to ensure it has all the settings you
|
||||||
If in doubt, simply disable WEB_CONFIGURE after use.
|
want. There are some further configuration options in there that
|
||||||
|
install.sh hasn't asked you about.
|
||||||
|
|
||||||
Should you need to access the configuration tool from a remote host,
|
Every time you change that file you need to feed it to the
|
||||||
using a tunneling technology like ssh is probably the safest approach.
|
psyconf command which will generate several control files for
|
||||||
If that is not an option you need to put the IP number of your browsing
|
your psyced installation. Editing those files by hand is not
|
||||||
client (or an abbreviation of it, like "127.0.0." with a trailing dot)
|
recommended as a new call to 'psyconf' will simply delete any
|
||||||
into the local/hosts.h file in your configuration directory.
|
manual changes.
|
||||||
The syntax is something like:
|
|
||||||
|
|
||||||
#define ENABLE_HOSTS "192.168.0.1"
|
We also have a very neat web-based configuration tool. Unfortunately
|
||||||
|
it hasn't been updated to work with the new configuration strategy.
|
||||||
If the IP number is only dynamic, it is certainly a good idea to
|
Still, 'psyconf' is enough for most things.
|
||||||
remove that entry after web configuration is complete.
|
|
||||||
|
|
||||||
|
|
||||||
4. Troubleshooting
|
4. Troubleshooting
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
LDMUD will compile TLS in, even if you told install.sh not to use it.
|
* Should you attempt to run psyced as root, you may later experience problems
|
||||||
|
running it under the uid you actually were planning to use, because files
|
||||||
|
have been generated that belong to root. 'chown -R ' repairs that.
|
||||||
|
|
||||||
|
* Should erq refuse to compile, your system might be providing a less recent
|
||||||
|
resolver library. Add '-lresolv' manually to LIBS in the Makefile and
|
||||||
|
re-issue 'make' (theroue had this effect on Slackware).
|
||||||
|
|
||||||
|
* We recently had a bug in the install.sh by which the line in the 'mypsyced'
|
||||||
|
file which is in charge of calling ./configure was broken in two and thus
|
||||||
|
only one half of the flags were used. Should you find #undef TLS in your
|
||||||
|
config.h it is quite likely that 'mypsyced' is literally broken in two.
|
||||||
|
|
||||||
|
* The LPC driver will have TLS in, even if you told install.sh not to use it.
|
||||||
This allows you to change your mind later on and shouldn't be a problem,
|
This allows you to change your mind later on and shouldn't be a problem,
|
||||||
but if it is, edit src/config.h to #undef USE_TLS and redo the compilation.
|
but if it is, edit src/config.h to #undef USE_TLS and redo the compilation.
|
||||||
|
|
||||||
There is a problem specific to the LDMUD 3.3.610 version, when it comes to
|
* Recent variants of psyclpc and LDMUD complain when you compile TLS in, then
|
||||||
compilation: It doesn't set the #define USE_TLS properly in config.h even
|
don't have a certificate to go with it. You can safely ignore it. This and
|
||||||
if the configure settings file tells it to. Please edit src/config.h
|
related messages are harmless and need no treatment:
|
||||||
accordingly and recompile. Other than that 610 is very stable and a good
|
'SSL error:02001002:system library:fopen:No such file or directory.'
|
||||||
choice!
|
|
||||||
|
|
||||||
You may also have to add the --tls-key options into the commandline
|
* There are however recent problems with gnutls. psyclpc and LDMUD are being
|
||||||
in bin/psycmuve. Just look into it and you'll see what I mean.
|
used with openssl in most cases, so the gnutls interface may not be up to
|
||||||
|
date. If you encounter problems, try installing openssl.
|
||||||
|
|
||||||
If you still encounter problems, please read (Questions and Answers)
|
* Should it look for the lpc driver in /usr/sbin although you have it
|
||||||
at the beginning of this document.
|
elsewhere, then psyconf got the architecture guessing wrong. Come
|
||||||
|
into the chat and show us the first lines of psyconf output, so
|
||||||
|
we can fix that.
|
||||||
|
|
||||||
|
* Sometimes installation problems can be fixed by running a cvs update
|
||||||
|
on install.sh and bin/psyconf, if they are new and just recently corrected.
|
||||||
|
If your install.sh doesn't appear updateable, look into the installation
|
||||||
|
directory - there is another copy. Run 'cvs update install.sh' then copy
|
||||||
|
it back to where you need it.
|
||||||
|
|
||||||
|
* Should you see the message "Failed to load master object 'secure/master'!"
|
||||||
|
when starting the driver, then you compiled it without the psyced.settings
|
||||||
|
which the installation process should have used automatically. You can
|
||||||
|
find them in the config directory.
|
||||||
|
|
||||||
|
* "tls_init_connection(): TLS layer hasn't been initialized." usually
|
||||||
|
happens when you are connecting a TLS port with no TLS on the client
|
||||||
|
side. But it can also mean that psyclpc didn't successfully read its
|
||||||
|
key and certificate from the start. Are the permissions correct?
|
||||||
|
What is psyclpc telling you right after starting up? Is it able to
|
||||||
|
read your key and certificate file?
|
||||||
|
|
||||||
|
* If you make any costum modifications to the psyced source code, you may
|
||||||
|
run into CVS collisions when running the psyced -u command to
|
||||||
|
fetch updates. Pay attention to its output, and inspect any file that
|
||||||
|
was marked with a 'C' (as in collision) manually for repairs.
|
||||||
|
If you already updated it, you can look for collisions in the output of
|
||||||
|
psyced -d, the command to see differences between the repository
|
||||||
|
and your local copy of the software.
|
||||||
|
|
||||||
|
* If you still encounter problems, please read (Questions and Answers)
|
||||||
|
at the beginning of this document. And, as always, come to the developer
|
||||||
|
chatroom!
|
||||||
|
|
||||||
|
|
||||||
5. Conclusion
|
5. Success!
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
You can now move on to the FIRSTSTEPS document.
|
You can now move on to the FIRSTSTEPS document.
|
||||||
Here's the online version, but you have one on your harddisk too.
|
Here's the online version, but you have one on your harddisk too.
|
||||||
[11]http://muve.pages.de/FIRSTSTEPS
|
[10]http://www.psyced.org/FIRSTSTEPS
|
||||||
|
|
||||||
This document was written by [12]psyc://ve.symlynX.com/~lynX
|
|
||||||
and [13]psyc://ve.symlynX.com/~real.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
This document was written by [11]psyc://psyced.org/~lynX
|
||||||
|
and Marek Schneider ([12]psyc://ve.symlynX.com/~real).
|
||||||
|
|
||||||
--
|
--
|
||||||
http://muve.pages.de/INSTALL.html
|
http://www.psyced.org/INSTALL.html
|
||||||
last change by lynx on fly at 2005-09-28 20:58:36 MEST
|
last change by lynx on lectern at 2009-01-27 23:32:29 CET
|
||||||
|
|
||||||
References
|
References
|
||||||
|
|
||||||
1. http://muve.pages.de/FIRSTSTEPS
|
1. http://www.psyced.org/FIRSTSTEPS
|
||||||
2. http://muve.pages.de/ldmud
|
2. http://www.psyced.org/
|
||||||
3. irc://ve.symlynX.com/psyc
|
3. http://lpc.psyc.eu/
|
||||||
4. telnet://ve.symlynX.com/
|
4. irc://psyced.org/#welcome
|
||||||
5. http://ve.symlynX.com:33333/PSYC/
|
5. http://psyced.org/PSYC/
|
||||||
6. http://www.gnu.org/
|
6. telnet://psyced.org/
|
||||||
7. http://www.sunfreeware.com/
|
7. http://www.gnu.org/
|
||||||
8. http://lpc.pages.de/
|
8. http://www.sunfreeware.com/
|
||||||
9. http://muve.pages.de/dist/world/drivers/ldmud/patches/psycmuve
|
9. http://lpc.psyc.eu/
|
||||||
10. http://localhost:44444/net/http/configure
|
10. http://www.psyced.org/FIRSTSTEPS
|
||||||
11. http://muve.pages.de/FIRSTSTEPS
|
11. irc://psyced.org/lynX,isNick
|
||||||
12. irc://ve.symlynX.com/lynX,isNick
|
12. irc://ve.symlynX.com/real,isNick
|
||||||
13. irc://ve.symlynX.com/real,isNick
|
|
||||||
|
@ -119,7 +119,8 @@ _console_debug = 0
|
|||||||
;_charset_console = ISO-8859-15
|
;_charset_console = ISO-8859-15
|
||||||
; '0' is tranquility unless something serious happens. best choice.
|
; '0' is tranquility unless something serious happens. best choice.
|
||||||
; '1' gives you slightly interesting output and LPC development debug.
|
; '1' gives you slightly interesting output and LPC development debug.
|
||||||
; '2' or '3' is too much and too detailed. we only use this as shown below.
|
; '2' or '3' is too much and too detailed. don't use it globally, as it
|
||||||
|
; may even trigger exceptions. use it only with _extra_debug below.
|
||||||
_level_debug = 0
|
_level_debug = 0
|
||||||
; Advanced extra debug flags for the psyclpc command line. You can debug
|
; Advanced extra debug flags for the psyclpc command line. You can debug
|
||||||
; specific parts of psyced like for example the textdb subsystem by adding
|
; specific parts of psyced like for example the textdb subsystem by adding
|
||||||
|
@ -1035,7 +1035,7 @@ _config_HTTP = ${HTTPCONFIG_10}
|
|||||||
_console_debug = $CONSOLE_10
|
_console_debug = $CONSOLE_10
|
||||||
; '0' is tranquility unless something serious happens. best choice.
|
; '0' is tranquility unless something serious happens. best choice.
|
||||||
; '1' gives you slightly interesting output and LPC development debug.
|
; '1' gives you slightly interesting output and LPC development debug.
|
||||||
; '2' or '3' is too much and too detailed. we only use this as _extra_debug.
|
; '2' or '3' is too much and too detailed. don't use it globally, as it ; may even trigger exceptions. use it only with _extra_debug below.
|
||||||
_level_debug = $DEBUG
|
_level_debug = $DEBUG
|
||||||
; Advanced extra debug flags for the psyclpc command line. You can debug
|
; Advanced extra debug flags for the psyclpc command line. You can debug
|
||||||
; specific parts of psyced like for example the textdb subsystem by adding
|
; specific parts of psyced like for example the textdb subsystem by adding
|
||||||
|
Loading…
Reference in New Issue
Block a user