ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/svn/hopm/trunk/INSTALL
(Generate patch)

Comparing hopm/trunk/INSTALL (file contents):
Revision 5052 by michael, Mon Dec 22 11:56:03 2014 UTC vs.
Revision 5060 by michael, Mon Dec 22 13:54:58 2014 UTC

# Line 6 | Line 6 | Make
6      1. ./configure
7      2. make
8      3. make install
9 <    4. cd $HOME/bopm
10 <    5. edit $HOME/bopm/etc/bopm.conf to suit
11 <    6. $HOME/bopm/bin/bopm
9 >    4. cd $HOME/hopm
10 >    5. edit $HOME/hopm/etc/hopm.conf to suit
11 >    6. $HOME/hopm/bin/hopm
12  
13      In detail:
14  
15      ./configure has a few options which you might need:
16  
17 <    --prefix            Sets the root of BOPM's install.  By default this
18 <                        is $HOME/bopm, with binaries going in
19 <                        $HOME/bopm/bin, config in $HOME/bopm/etc and logs
20 <                        in $HOME/bopm/var.
17 >    --prefix            Sets the root of HOPM's install.  By default this
18 >                        is $HOME/hopm, with binaries going in
19 >                        $HOME/hopm/bin, config in $HOME/hopm/etc and logs
20 >                        in $HOME/hopm/var.
21  
22      --bindir            Specify the place to install binaries.  By default
23                          this is $PREFIX/bin. (see --prefix, above)
# Line 33 | Line 33 | Make
33      configure at some point.  If you think you need to change these then we
34      assume you've read the code and know why.
35  
36 <    Compilation of BOPM requires GNU Make (usually 'gmake' on BSD systems).
36 >    Compilation of HOPM requires GNU Make (usually 'gmake' on BSD systems).
37  
38   Configuration
39   -------------
40  
41 <    Edit bopm.conf as needed.  Most options are self explanatory and
41 >    Edit hopm.conf as needed.  Most options are self explanatory and
42      contain a short description.
43  
44      Please take note of the target_string, this is new in version 2 onward and may be
45      different for your ircd.  Because we now check that we really have
46 <    connected back onto IRC, BOPM needs to be told what your ircd says during
46 >    connected back onto IRC, HOPM needs to be told what your ircd says during
47      the first part of a connection.  If you're not sure, the best thing to do
48      is telnet to your ircd from your shell, e.g.:
49  
50 <      [andy@fullers bopm]$ telnet porkscratchings.someserver.org 6667
50 >      [andy@fullers hopm]$ telnet porkscratchings.someserver.org 6667
51        Trying 207.8.219.202...
52        Connected to porkscratchings.someserver.org.
53        Escape character is '^]'.
54 <      :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Looking up your hostname...
54 >      :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Looking up your hostname
55        :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Checking Ident
56        :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Got Ident response
57        :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Found your hostname
# Line 81 | Line 81 | Configuration
81   Execution
82   ---------
83  
84 <    You can run BOPM from any directory, the path to its config file is
84 >    You can run HOPM from any directory, the path to its config file is
85      compiled into it.  The bot will fork and connect to the IRC server
86      immediately.  Any errors and debug information can be found in
87 <    $PREFIX/var/bopm.log.
87 >    $PREFIX/var/hopm.log.
88  
89 <    You can tell BOPM to use a different config file with the -c argument,
89 >    You can tell HOPM to use a different config file with the -c argument,
90      this works the same way that wgmon's -c argument does, just give the name
91      of the config file not including the ".conf".  This also affects the log
92 <    and PID files i.e. ./bopm -c myserver will read from myserver.conf, log to
92 >    and PID files i.e. ./hopm -c myserver will read from myserver.conf, log to
93      myserver.log and write PID to myserver.pid.  If you do not use -c, the
94 <    files bopm.conf, bopm.log and bopm.pid will be used by default.  This can
95 <    be altered in options.h.  This is useful for running multiple BOPM on
94 >    files hopm.conf, hopm.log and hopm.pid will be used by default.  This can
95 >    be altered in options.h.  This is useful for running multiple HOPM on
96      the same host.
97  
98      Further debugging can be enabled by using one or more -d switches.  One or

Diff Legend

Removed lines
+ Added lines
< Changed lines (old)
> Changed lines (new)