Changes in / [1bf9492:ddd4779]

4 edited


  • bitlbee.conf

    r1bf9492 rddd4779  
    1111##  Inetd -- Run from inetd (default)
    12 ##  Daemon -- Run as a stand-alone daemon -- EXPERIMENTAL! BitlBee is not yet
    13 ##    stable enough to serve lots of users from one process. Because of this
    14 ##    and other reasons, the use of daemon-mode is *STRONGLY* discouraged,
    15 ##    don't even *think* of reporting bugs when you use this.
     12##  Daemon -- Run as a stand-alone daemon, serving all users from one process.
     13##    This saves memory if there are more users, the downside is that when one
     14##    user hits a crash-bug, all other users will also lose their connection.
    1615##  ForkDaemon -- Run as a stand-alone daemon, but keep all clients in separate
    1716##    child processes. This should be pretty safe and reliable to use instead
  • conf.c

    r1bf9492 rddd4779  
    132132                                "\n"
    133133                                "  -I  Classic/InetD mode. (Default)\n"
    134                                 "  -D  Daemon mode. (Still EXPERIMENTAL!)\n"
     134                                "  -D  Daemon mode. (one process serves all)\n"
    135135                                "  -F  Forking daemon. (one process per client)\n"
    136136                                "  -u  Run daemon as specified user.\n"
  • doc/README

    r1bf9492 rddd4779  
    5656a package from your distro would've been a better idea. :-P)
     58Note that the BitlBee code is getting stable enough for daemon mode to be
     59useful. Some public servers use it, and it saves a lot of memory by serving
     60tens of users from a single process. One crash affects all users, but these
     61are becoming quite rare.
    98103versions of make, we'd love to hear it, but it seems this just isn't
    103 ==================================
    105 BitlBee is not yet bug-free. Sometimes a bug causes the program to get into
    106 an infinite loop. Something you really don't want on a public server,
    107 especially when that machine is also used for other (mission-critical) things.
    108 For now we can't do much about it. We haven't seen that happen for a long
    109 time already on our own machines, but some people still manage to get
    110 themselves in nasty situations we haven't seen before.
    112 For now the best we can offer against this problem is bitlbeed, which allows
    113 you to setrlimit() the child processes to use no more than a specified
    114 number of CPU seconds. Not the best solution (not really a solution anyway),
    115 but certainly trashing one busy daemon process is better than trashing your
    116 whole machine.
    118 We don't believe adding a limit for bitlbee to /etc/security/limits.conf will
    119 work, because that file is only read by PAM (ie just for real login users,
    120 not daemons).
    122 See utils/bitlbeed.c for more information about the program.
    124 Just a little note: Now that we reach version 1.0, this shouldn't be that
    125 much of an issue anymore. However, on a public server, especially if you
    126 also use it for other things, it can't hurt to protect yourself against
    127 possible problems.
  • doc/bitlbee.8

    r1bf9492 rddd4779  
    4545\fBbitlbee\fP should be called by
    46 .BR inetd (8).
    47 (Or \fBbitlbeed\fP,
    48 if you can't run and/or configure \fBinetd\fP.) There is an experimental
    49 daemon mode too, in which BitlBee will serve all clients in one process
    50 (and does not require inetd), but this mode is still experimental.
    51 There are still some bugs left in BitlBee, and if they cause a crash,
    52 that would terminate the BitlBee connection for all clients.
     46.BR inetd (8),
     47or you can run it as a stand-alone daemon.
    5449.SH OPTIONS
    6257Run in daemon mode. In this mode, BitlBee forks to the background and
    6358waits for new connections. All clients will be served from one process.
    64 This is still experimental. See the note above for more information.
    6559.IP "-F"
    6660Run in ForkDaemon mode. This is similar to ordinary daemon mode, but every
    67 client gets its own process. Easier to set up than inetd mode, but without
     61client gets its own process. Easier to set up than inetd mode, and without
    6862the possible stability issues.
    6963.IP "-i \fIaddress\fP"
Note: See TracChangeset for help on using the changeset viewer.