Changeset 2cdd8ce for doc/README
- Timestamp:
- 2005-11-19T15:17:03Z (19 years ago)
- Branches:
- master
- Children:
- 9c8ae50, b20b32f
- Parents:
- c998255 (diff), 94281ef (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/README
rc998255 r2cdd8ce 9 9 make install will move all the files to the right places. 10 10 11 --- inetd installation 12 11 13 After installation you have to set up inetd (you got that one running, 12 14 right? If not, just take a look at utils/bitlbeed.c) to start BitlBee. You … … 18 20 of just 'nobody') might be a good idea. 19 21 22 *BSD/Darwin/OSX NOTE: Most *BSD inetds are more scrict than the one that 23 comes with Linux systems. Possibly all non-Linux inetds are like this. They 24 don't allow you to specify a port number in the inetd.conf entry, instead 25 you have to put a service name there (one that is also mentioned in 26 /etc/services). So if there's no line in /services for 6667/tcp (or whatever 27 you choose), add it and use that name in the inetd.conf entry. 28 29 -- xinetd installation 30 31 Most machines use xinetd instead of inetd these days. If your machine runs 32 xinetd, you can copy the bitlbee.xinetd file from the doc/ directory to your 33 xinetd.d/ directory. Most likely you'll have to change a thing or two before 34 it'll work. 35 36 After configuring your (x)inetd, send the daemon a SIGHUP and things should 37 work. If not, see your syslogs, since both daemons will complain there when 38 something's wrong. 39 20 40 Also, don't forget to create the configuration directory (/var/lib/bitlbee/ 21 41 by default) and chown it to the UID BitlBee is running as. Make sure this 22 42 directory is read-/writable by this user only. 23 24 (For xinetd users a xinetd configuration file is included: doc/bitlbee.xinetd)25 43 26 44 … … 48 66 ================== 49 67 50 FreeBSD NOTE: It looks like FreeBSD does allow port numbers instead of service51 names in inetd.conf, as long as the service for this port exists in52 /etc/services. Linux isn't this strict. If you got problems in FreeBSD, just53 add a line for your chosen port number to /etc/services.54 55 Darwin/Mac OS X is even more strict; you should add a bitlbee service to56 /etc/services and use that name in inetd.conf. Not really a problem, since57 that's the cleanest way of doing this on any operating system anyway.58 59 68 Cygwin NOTE: You'll need a glib installation to run BitlBee. However, Cygwin 60 69 doesn't provide a glib package. You can download a binary tar.gz from: … … 66 75 Please do report them, we might be able to fix them if they're not too 67 76 mysterious. 77 78 Also, the configure script is known to not work very well with non-Bash 79 shells, so if you experience problems, make sure you use bash to run the 80 script. Same for the Makefile, it only works well with GNU make. (gmake on 81 most BSD systems) 82 83 If someone can tell us how to write Makefiles that work with both/all 84 versions of make, we'd love to hear it, but it seems this just isn't 85 possible. 68 86 69 87
Note: See TracChangeset
for help on using the changeset viewer.