Reputation
3,572
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
8 20
Newest
 Yearling
Impact
~270k people reached

Dec
20
answered password-less ssh works to connect to one user on a remote machine but not another
Dec
20
answered What are my options for centralizing Unix user management
Dec
20
answered Giving other users write access to apache logs can result in root exploit - How does this work?
Dec
20
answered How to prevent bombardment of hack attempts on VPS
Dec
20
comment Replacing Hard Drives
The major issue I've seen is vibration. I know of a dedicated server provider that used to put towers on metal racks. The racks bow in the middle. The servers vibrated significantly and touched each other. We saw a 10x higher than expected drive failure rate. At the facility were trash cans full of disks. When the same facility moved to proper rack mounts this failure rate declined.
Dec
19
awarded  Good Answer
Dec
19
awarded  Mortarboard
Dec
19
awarded  Nice Answer
Dec
19
answered Replacing Hard Drives
Dec
19
comment Adding multiple A records for same host for backup purpose
Given your new question, I think we will need more details. What risk are you trying to mitigate with an HA solution? Power failure, network, web application, etc. requires different solutions.
Dec
19
answered DNS Not Resolving For All Users
Dec
19
comment Graphical Ping utility with logging
Would have to second this recommendation.
Dec
19
answered Updating OpenSSH to latest stable version via yum
Dec
19
comment Deploying git repo on production server without account password
Not sure if it will work in your use case, but check into using SSH-Agent to cache the passphrase for the ssh key.
Dec
14
answered Permission, apache user and www folder in Linux
Dec
14
answered Server not coping, cpu load averages spike to 33.0
Dec
14
answered Shared webhost IP blacklisted and is stopping my legitimate emails sending
Dec
12
answered Should I rate-limit packets with iptables?
Dec
12
comment NGINX timeout after +200 concurrent connections
added updated to main reply due to code.
Dec
12
revised NGINX timeout after +200 concurrent connections
added 521 characters in body