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 [2018/02/13 12:37] – Added some information on binding to ports below 1024 as non-root on Linux, since that question seems to come up from time to time nightfox | faq:nix [2020/11/14 11:19] – Create Linux-recycle FAQ digital man | ||
---|---|---|---|
Line 18: | Line 18: | ||
* [[# | * [[# | ||
* [[#Disk space|How much disk space is required]]? | * [[#Disk space|How much disk space is required]]? | ||
- | * [[#TermType|What does an '' | + | * [[#Terminal Type|What does an '' |
- | * [[#ports_below_1024_without_root_on_linux|How can I bind to ports below 1024 without being root on Linux]]? | + | * [[#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 170: | Line 172: | ||
**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. | + | |
Line 193: | Line 194: | ||
To elaborate, [[util: | To elaborate, [[util: | ||
- | ===== Ports Below 1024 Without Root On Linux ===== | + | ===== SDL errors |
- | By default, Linux does not allow non-root processes to bind to ports below 1024. This was done as a security measure, although some argue that the reasons for this are obsolete. It is often a bad practice to run processes as root unless it's really necessary to do so, and perhaps even more so with an Internet-accessible server. | + | **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 | ||
+ | |||
+ | Work-arounds: | ||
+ | - Clean re-build all of Synchronet without SDL support (include '' | ||
+ | - Set the '' | ||
+ | |||
+ | ===== Recycle ===== | ||
+ | **Question: | ||
+ | Why do my servers/ | ||
+ | |||
+ | **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 '' | ||
+ | | ||
+ | - **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 " | ||
- | For more information, | + | The solution is to remove |
- | [[https:// | + | |
- | [[https://www.jumpingbean.co.za/ | + | |
- | [[https:// | + | |
===== See Also ===== | ===== See Also ===== |