Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faq:nix [2010/04/01 11:34] – deuce | faq:nix [2022/06/12 14:09] – [Maximum Open Files] Mention the fixed bug that could cause this. digital man | ||
---|---|---|---|
Line 15: | Line 15: | ||
* [[#X Windows|Does Synchronet for Unix require X Windows]]? | * [[#X Windows|Does Synchronet for Unix require X Windows]]? | ||
* [[#GUI|Is there a graphic user interface for Unix sysops]]? | * [[#GUI|Is there a graphic user interface for Unix sysops]]? | ||
- | * [[# | + | * [[# |
* [[# | * [[# | ||
* [[#Disk space|How much disk space is required]]? | * [[#Disk space|How much disk space is required]]? | ||
+ | * [[#Terminal Type|What does an '' | ||
+ | * [[#tempnam warning|Why do I get a warning about use of '' | ||
+ | * [[#SDL Errors|How do I work around SDL 1.2 run-time errors]]? | ||
+ | * [[# | ||
+ | * [[# | ||
| | ||
===== Flavors ===== | ===== Flavors ===== | ||
Line 26: | Line 31: | ||
**Answer: | **Answer: | ||
Currently there are four levels of support for Unix-like OSs. | Currently there are four levels of support for Unix-like OSs. | ||
- | - Operating systems and platforms which are actively used by the developers. These are always expected to work correctly. | + | - Operating systems and platforms which are actively used by the developers. These are always expected to work correctly. |
- Platforms which have been ran by developers and an attempt to maintain support is exerted. | - Platforms which have been ran by developers and an attempt to maintain support is exerted. | ||
- Next there is non-x86 hardware with one of the above OSs. We try to ensure that Synchronet works on these platforms, but a bug report may be ignored for months before it is resolved due to lack of access to the platform. | - Next there is non-x86 hardware with one of the above OSs. We try to ensure that Synchronet works on these platforms, but a bug report may be ignored for months before it is resolved due to lack of access to the platform. | ||
Line 37: | Line 42: | ||
**Answer: | **Answer: | ||
- | Should work with any GNU/ | + | Should work with any GNU/ |
===== 64-bit ===== | ===== 64-bit ===== | ||
Line 45: | Line 50: | ||
**Answer: | **Answer: | ||
- | Untested experimental support for 64-bit | + | 64-bit |
- | directions available | + | |
- | [[http:// | + | |
- | in conjunction with this document for building and be prepared to deal with | + | |
- | bugs. | + | |
===== Installer ===== | ===== Installer ===== | ||
Line 65: | Line 66: | ||
**Question: | **Question: | ||
- | Are non-x86 (Alpha, SPARC, 68k, PowerPC, etc) processors supported? | + | Are non-x86/x64 (Alpha, SPARC, 68k, PowerPC, etc) processors supported? |
**Answer: | **Answer: | ||
Not currently. Synchronet assumes a little-endian processor. It *may* work | Not currently. Synchronet assumes a little-endian processor. It *may* work | ||
on other little-endian processors (e.g. Alpha), but hasn't been tested. | on other little-endian processors (e.g. Alpha), but hasn't been tested. | ||
- | Big-endian support is currently being developed for the v3.20 time-frame. | ||
===== Download ===== | ===== Download ===== | ||
Line 78: | Line 78: | ||
**Answer: | **Answer: | ||
- | There are no binary distributions at this time, so you must get the source | + | See the step-by-step instructions |
- | code from the Synchronet CVS repository (see the step-by-step instructions | + | |
- | below for details) or by downloading the latest verified buildable source | + | |
- | code tarball (tgz file) from ftp:// | + | |
===== Binaries ===== | ===== Binaries ===== | ||
Line 123: | Line 120: | ||
programs. | programs. | ||
- | There' | + | For running external DOS programs on Linux using DOSEMU, see [[howto:dosemu]] for details. |
- | http:// | + | |
- | (mirror) http:// | + | |
- | + | ||
- | and a FAQ for using DOSEMU with Synchronet for Linux (without a patch): | + | |
- | http:// | + | |
===== Doors ===== | ===== Doors ===== | ||
Line 163: | Line 154: | ||
Yes, currently Synchronet has successfully been built with GCC, ICC | Yes, currently Synchronet has successfully been built with GCC, ICC | ||
(The Intel C Compiler), and Clang/ | (The Intel C Compiler), and Clang/ | ||
- | '' | + | '' |
- | icc is the C compiler name and icpc is the C++ compiler name. If you get | + | and icpc is the C++ compiler name. If you get errors during the build (not |
- | errors during the build (not warnings) please submit a bug report. | + | warnings) please submit a bug report. |
- | are using a commercial compiler other than ICC, we will probably be unable | + | other than ICC, we will probably be unable to help you without a copy of the |
- | to help you without a copy of the compiler. | + | compiler. |
===== SELinux ===== | ===== SELinux ===== | ||
Line 174: | Line 165: | ||
**Answer: | **Answer: | ||
- | Yes, you'll need to use chcon on each of the shared objects (.so files) | + | Yes, you'll need to use chcon on each of the Synchronet |
- | chcon -t texrel_shlib_t /path/to/libwhatever.so | + | chcon -t texrel_shlib_t /sbbs/exec/*.so |
- | Do this for each .so file that Synchronet creates. | + | |
===== Disk Space ===== | ===== Disk Space ===== | ||
Line 183: | Line 173: | ||
**Answer: | **Answer: | ||
- | A fresh install (as of Feb-2009) requires about 70MBytes. | + | A fresh install (as of Mar-2020) from source code, requires about 500MBytes of space. |
- | Much of the space consumed is in the form of intermediate build files which | + | Much of the space consumed is in the form of intermediate build files which may be removed after the build is complete if space is a concern. |
- | may be removed after the build is complete if space is a concern. | + | |
+ | |||
+ | ===== Terminal Type ===== | ||
+ | **Question: | ||
+ | What does the error '' | ||
+ | |||
+ | **Answer: | ||
+ | The error indicates that the value of your '' | ||
+ | |||
+ | The default value of the '' | ||
+ | |||
+ | ===== tempnam warning ===== | ||
+ | **Question: | ||
+ | Why do I get the GCC compilation warning: < | ||
+ | |||
+ | **Answer: | ||
+ | This is not an error but a harmless warning. You can safely ignore it. | ||
+ | |||
+ | To elaborate, [[util: | ||
+ | |||
+ | ===== SDL errors ===== | ||
+ | **Question: | ||
+ | How do I work around SDL_main errors (e.g. '' | ||
+ | < | ||
+ | $ / | ||
+ | No protocol specified | ||
+ | No protocol specified | ||
+ | No protocol specified | ||
+ | Segmentation fault (core dumped) | ||
+ | </ | ||
+ | |||
+ | **Answer: | ||
+ | Double check that you can run X applications (e.g. '' | ||
+ | xhost +SI: | ||
+ | executed before switching to another user account (e.g. with '' | ||
+ | |||
+ | Work-arounds: | ||
+ | - Clean re-build all of Synchronet without SDL support (include '' | ||
+ | - Set the '' | ||
+ | |||
+ | ===== Recycle ===== | ||
+ | **Question: | ||
+ | Why do my servers/ | ||
+ | |||
+ | **Answer: | ||
+ | Servers will not recycle while they are in-use. | ||
+ | |||
+ | < | ||
+ | $ node rerun | ||
+ | |||
+ | Synchronet Node Display/ | ||
+ | |||
+ | Node 1: User #1 reading messages via telnet (M) [R] | ||
+ | Node 2: Waiting for connection [R] | ||
+ | Node 3: Waiting for connection [R] | ||
+ | Node 4: Waiting for connection [R] | ||
+ | Node 5: Waiting for connection [R] | ||
+ | Node 6: Waiting for connection [R] | ||
+ | Node 7: Waiting for connection [R] | ||
+ | Node 8: Waiting for connection [R] | ||
+ | </ | ||
+ | |||
+ | **Question: | ||
+ | What do the following warning-level log messages indicate? | ||
+ | Disabling Terminal Server recycle support | ||
+ | Disabling FTP Server recycle support | ||
+ | Disabling Web Server recycle support | ||
+ | Disabling Mail Server recycle support | ||
+ | Disabling Services recycle support | ||
+ | |||
+ | **Answer: | ||
+ | Recycle support can be disabled manually be setting the '' | ||
+ | The log warning messages above (" | ||
+ | - Configured to bind-to/ | ||
+ | - **and** the BBS was configured to change the current user-id in the '' | ||
+ | - **and** the BBS could not dynamically set the bind capabilities using the Linux " | ||
+ | |||
+ | The solution is to remove the '' | ||
+ | |||
+ | ===== Maximum Open Files ===== | ||
+ | **Question: | ||
+ | Why am I seeing '' | ||
+ | |||
+ | **Answer: | ||
+ | Versions of Synchronet prior to v3.19c contained a bug with the JavaScript //User// class that could cause a leak of open file descriptors (concurrent opens of the '' | ||
+ | |||
+ | **Answer: | ||
+ | You need to increase your maximum number of open files. | ||
+ | \\ \\ | ||
+ | **Checking current open file limits**\\ | ||
+ | The most reliable way to determine your open file limit is to login to your BBS as a sysop, run the ''; | ||
+ | |||
+ | Soft limit: '' | ||
+ | Hard limit: '' | ||
+ | |||
+ | **If you start Synchronet with systemd**\\ | ||
+ | If you're using [[howto: | ||
+ | |||
+ | <file sbbs.service> | ||
+ | LimitNOFILE=10000 | ||
+ | </ | ||
+ | |||
+ | After adding the line, reload the service file from the command line using '' | ||
+ | |||
+ | **If you start Synchronet manually or with a shell script**\\ | ||
+ | If you start sbbs with a shell script, manually from the command line, or some other similar method, edit ''/ | ||
+ | |||
+ | To raise the soft limit for your Synchronet user, add this line: | ||
+ | |||
+ | <file limits.conf> | ||
+ | yourBBSuser | ||
+ | </ | ||
+ | | ||
===== See Also ===== | ===== See Also ===== | ||
* [[: | * [[: |