Changes in / [b6cd9e9:783e9b7]


Ignore:
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • bitlbee.conf

    rb6cd9e9 r783e9b7  
    1010##
    1111##  Inetd -- Run from inetd (default)
    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.
     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.
    1516##  ForkDaemon -- Run as a stand-alone daemon, but keep all clients in separate
    1617##    child processes. This should be pretty safe and reliable to use instead

  • conf.c

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

  • doc/README

    rb6cd9e9 r783e9b7  
    5656a package from your distro would've been a better idea. :-P)
    5757
    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.
    62 
    6358
    6459DEPENDENCIES
    … …  
    10398versions of make, we'd love to hear it, but it seems this just isn't
    10499possible.
     100
     101
     102RUNNING ON SERVERS WITH MANY USERS
     103==================================
     104
     105BitlBee is not yet bug-free. Sometimes a bug causes the program to get into
     106an infinite loop. Something you really don't want on a public server,
     107especially when that machine is also used for other (mission-critical) things.
     108For now we can't do much about it. We haven't seen that happen for a long
     109time already on our own machines, but some people still manage to get
     110themselves in nasty situations we haven't seen before.
     111
     112For now the best we can offer against this problem is bitlbeed, which allows
     113you to setrlimit() the child processes to use no more than a specified
     114number of CPU seconds. Not the best solution (not really a solution anyway),
     115but certainly trashing one busy daemon process is better than trashing your
     116whole machine.
     117
     118We don't believe adding a limit for bitlbee to /etc/security/limits.conf will
     119work, because that file is only read by PAM (ie just for real login users,
     120not daemons).
     121
     122See utils/bitlbeed.c for more information about the program.
     123
     124Just a little note: Now that we reach version 1.0, this shouldn't be that
     125much of an issue anymore. However, on a public server, especially if you
     126also use it for other things, it can't hurt to protect yourself against
     127possible problems.
    105128
    106129

  • doc/bitlbee.8

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