Changes

Jump to: navigation, search

Funtoo Compute Initiative

1,587 bytes added, 4 years ago
no edit summary
The network and initial server configuration will be covered in more detail below.
 
=== Recommended Ebuilds ===
 
The following ebuilds are recommended as part of a Funtoo server deployment. First, {{Package|sys-apps/haveged}} is recommended. For what purpose? Well, the Linux kernel maintains its own internal entropy (randomness) source, which is actually an essential component for encryption. This entropy source is kept viable by injecting it with a lot random timing information from user input -- but on a headless server, this entropy injection doesn't happen nearly as much as it needs to. In addition, we are going to potentially be running hundreds of OpenSSH daemons and other entropy-hungry apps. The solution is to run [http://www.issihosts.com/haveged/ haveged]] which will boost the available entropy on our headless server:
 
{{console|body=
# ##i##emerge -av sys-apps/haveged
# ##i##rc-update add haveged default
}}
 
Mcelog is essential for detecting ECC memory failure conditions. Any such conditions will be logged to {{f|/var/log/mcelog}}:
 
{{console|body=
# ##i##emerge -av app-admin/mcelog
# ##i##rc-update add mcelog default
}}
 
Smartmontools should be configured to monitor for pre-emptive disk failure for all your disks:
 
{{console|body
# ##i##emerge -av sys-apps/smartmontools
# ##i##rc-update add smartd default
}}
 
Ensure lines similar to the following appear in your {{f|/etc/smartd.conf}}:
 
{{file|name=/etc/smartd.conf|body=
# -M test also ensures that a test alert email is sent when smartd is started or restarted, in addition to regular monitoring
DEVICESCAN -M test -m me@email.com
# Remember to put a valid email address, above ^^
}}
Bureaucrats, Administrators, wiki-admins, wiki-staff
6,342
edits

Navigation menu