diff options
| author | Wilmer van der Gaast <wilmer@gaast.net> | 2008-05-24 12:57:47 -0700 |
|---|---|---|
| committer | Wilmer van der Gaast <wilmer@gaast.net> | 2008-05-24 12:57:47 -0700 |
| commit | de8e584d7f4fea214934af094a4df2672d7e0be8 (patch) | |
| tree | cbe36460efe2f23edc20501a00e94c97448d0b3d /bitlbee.conf | |
| parent | 92998915be47eab17e548af5c3dd43fa4eab9683 (diff) | |
Daemon mode is not an experiment anymore, it's running on testing.bitlbee.org
for two weeks already with >30 active connections and not a single crash.
Diffstat (limited to 'bitlbee.conf')
| -rw-r--r-- | bitlbee.conf | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/bitlbee.conf b/bitlbee.conf index c03a564f..5fce2820 100644 --- a/bitlbee.conf +++ b/bitlbee.conf @@ -9,10 +9,9 @@ ## RunMode: ## ## Inetd -- Run from inetd (default) -## Daemon -- Run as a stand-alone daemon -- EXPERIMENTAL! BitlBee is not yet -## stable enough to serve lots of users from one process. Because of this -## and other reasons, the use of daemon-mode is *STRONGLY* discouraged, -## don't even *think* of reporting bugs when you use this. +## Daemon -- Run as a stand-alone daemon, serving all users from one process. +## This saves memory if there are more users, the downside is that when one +## user hits a crash-bug, all other users will also lose their connection. ## ForkDaemon -- Run as a stand-alone daemon, but keep all clients in separate ## child processes. This should be pretty safe and reliable to use instead ## of inetd mode. |