-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since mine is a small deployment, I don't have strong feelings either way, although I'd find a single binary easier to deal with since I don't need the across-multiple-machines scalability of separate binaries.
But I'd like to suggest a solution: command line switches combined with a configuration setting. So the way you would see this is something like: ~$ jabberd -router ~$ jabberd -sm and on another machine you would execute ~$ jabberd -c2s ~$ jabberd -s2s with, as needed, and as configured on the first machine to not include router, you could have another machine yet, running /usr/bin/jabberd -router But for smaller places, like my installation, could have just a single configuration file, and run only a single executable, using IPC for communication b/w threads... ~$ jabberd & so, what do you guys think of that ... more complex than anybody wants to tackle? I'm still running 2.1.6 because it hasn't let anybody log in using the 2.1.23 installed in /tmp and I haven't tried the 2.2 branch yet for various reasons. Jad Shipman, Computer Specialist Fort Vancouver Regional Library -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.2 iQA/AwUBSEhBONRPHc/RSQHbEQKPYwCgyi8oGPIgSU9FqJrHQBPJ0MmKhs0An17f 4tWzml9f90MkZUA6lYFQciCu =XYli -----END PGP SIGNATURE----- -- To unsubscribe send a mail to [EMAIL PROTECTED]
