From 47a2b7ad9795c82f416bb3e83c40a5798329fba3 Mon Sep 17 00:00:00 2001
From: Alloy Networks <45832257+alloyxrp@users.noreply.github.com>
Date: Sat, 23 Mar 2019 15:56:01 +0200
Subject: [PATCH] Update system-requirements.md

---
 .../installation/system-requirements.md                      | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md
index 994cec351b..763aac2d33 100644
--- a/content/tutorials/manage-the-rippled-server/installation/system-requirements.md
+++ b/content/tutorials/manage-the-rippled-server/installation/system-requirements.md
@@ -13,6 +13,7 @@ A `rippled` server should run comfortably on commodity hardware, to make it inex
 
 Amazon EC2's `m3.large` VM size may be appropriate depending on your workload. A fast network connection is preferable. Any increase in a server's client-handling load increases resources needs.
 
+
 ## Recommended Specifications
 
 For best performance in enterprise production environments, Ripple recommends running `rippled` on bare metal with the following characteristics:
@@ -25,6 +26,10 @@ For best performance in enterprise production environments, Ripple recommends ru
   	- For production: 32GB
 - Network: Enterprise data center network with a gigabit network interface on the host
 
+## System Time
+
+A `rippled` server relies on maintaining accurate time. It is recommended that the system synchronize time using the Network Time Protocol (NTP) with daemons such as `ntpd` or `chrony`.
+
 ## See Also
 
 For more information on the recommended specifications and planning for production needs, see [Capacity Planning](capacity-planning.html).