2,187
edits
Difference between revisions of "Ubuntu"
Jump to navigation
Jump to search
→Initial Setup: Added "NTP"
(Added Python) |
(→Initial Setup: Added "NTP") |
||
| Line 146: | Line 146: | ||
# Install VM Tools | # Install VM Tools | ||
#* <code> apt-get install vmware-tools </code> | #* <code> apt-get install vmware-tools </code> | ||
=== NTP === | |||
''Not required if your server doesn't really need bang on accurate time'' | |||
Out of the box your server will sync every time its restarted and drift a bit in-between. There is an additional resource demand in running the NTP daemon so unless you need to, there's no need to. | |||
I tend to have one or two servers updating from remote (public) servers, and then all others updating from those. | |||
# Install the service | |||
#* <code> apt-get install ntp </code> | |||
# Update the NTP config file (eg for a server updating from public European servers - see http://www.pool.ntp.org/) | |||
#* <code> server 0.europe.pool.ntp.org </code> | |||
#* <code> server 1.europe.pool.ntp.org </code> | |||
#* <code> server 2.europe.pool.ntp.org </code> | |||
#* <code> server 3.europe.pool.ntp.org </code> | |||
#* Remove <code> noquery </code> from restrict lines to allow other servers to query this server | |||
# Restart the NTP service | |||
#* <code> service ntp restart </code> | |||
# Verify using the following commands | |||
#* <code> ntpq -np </code> | |||
#* <code> date </code> | |||
=== Update the OS === | === Update the OS === | ||