Changeset b925666 for doc


Ignore:
Timestamp:
2010-07-29T19:30:47Z (14 years ago)
Author:
Wilmer van der Gaast <wilmer@…>
Branches:
master
Children:
8b61469
Parents:
1521a85
Message:

Show a friendly warning message when running in inetd mode on the command
line (if stdin is a TTY). This hopefully answers a FAQ. Also moved stuff
around in README a little bit, daemon mode should be described before
obsolete inetd stuff.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • doc/README

    r1521a85 rb925666  
    99make install will move all the files to the right places.
    1010
    11 --- inetd installation
     11--- (Fork)Daemon mode
     12
     13These days ForkDaemon mode is the recommended way of running BitlBee. The
     14difference between Daemon and ForkDaemon mode is that in the latter, a
     15separate process is spawned for every user. This costs a little bit more
     16memory, but means that if one user hits a bug in the code, not all other
     17users get disconnected with him/her.
     18
     19To use BitlBee in any daemon mode, just start it with the right flags or
     20enable it in bitlbee.conf (see the RunMode option). You probably want to
     21write an init script to start BitlBee automatically after a reboot. (This
     22is where you realise using a package from your distro would've been a better
     23idea. :-P)
     24
     25Please do make sure that the user BitlBee runs as (not root, please!) is
     26able to read from and write to the /var/lib/bitlbee directory to save your
     27settings!
     28
     29--- inetd installation (more or less deprecated)
    1230
    1331After installation you have to set up inetd (you got that one running,
    … …  
    2745you choose), add it and use that name in the inetd.conf entry.
    2846
    29 -- xinetd installation
     47-- xinetd installation (equally deprecated)
    3048
    3149Most machines use xinetd instead of inetd these days. If your machine runs
    … …  
    4159by default) and chown it to the UID BitlBee is running as. Make sure this
    4260directory is read-/writable by this user only.
    43 
    44 --- (Fork)Daemon mode
    45 
    46 If you don't want to run any inetd daemon, you can run BitlBee in Daemon
    47 mode. Right now, daemon mode may be a bad idea on servers with multiple
    48 users, since possible fatal BitlBee bugs will crash the BitlBee process and
    49 disconnect all connected users at once. Instead, you can use ForkDaemon
    50 mode, which serves every user from a separate process, without depending on
    51 an inetd daemon.
    52 
    53 To use BitlBee in daemon mode, just start it with the right flags or enable
    54 it in bitlbee.conf. You probably want to write an init script to start
    55 BitlBee automatically after a reboot. (This is where you realise using
    56 a package from your distro would've been a better idea. :-P)
    57 
    58 Note that the BitlBee code is getting stable enough for daemon mode to be
    59 useful. Some public servers use it, and it saves a lot of memory by serving
    60 tens of users from a single process. One crash affects all users, but these
    61 are becoming quite rare.
    6261
    6362
    … …  
    139138http://bugs.bitlbee.org/
    140139
    141 Our version control system is Bazaar-NG. Our repository is at:
     140Our version control system is Bazaar. Our repository is at:
    142141http://code.bitlbee.org/
     142
     143More documentation on the Wiki:
     144http://wiki.bitlbee.org/
    143145
    144146
    … …  
    186188        BitlBee - An IRC to other chat networks gateway
    187189                  <http://www.bitlbee.org/>
    188         Copyright (C) 2002-2007  Wilmer van der Gaast <wilmer@gaast.net>
     190        Copyright (C) 2002-2010  Wilmer van der Gaast <wilmer@gaast.net>
    189191                                 and others
Note: See TracChangeset for help on using the changeset viewer.