Added ntp and 18901 and .bash_profile

Added ntp and 18901 and .bash_profile
AWS is fine. Its tc-tac01 who isn't fine:
```
core@tc-tac01 ~ $ sudo systemctl status ntpd.service
● ntpd.service - Network Time Service
   Loaded: loaded (/usr/lib64/systemd/system/ntpd.service; disabled)
   Active: failed (Result: exit-code) since Mon 2014-11-10 12:29:20 UTC; 3 weeks 6 days ago
  Process: 49622 ExecStart=/usr/sbin/ntpd -g -n -u ntp:ntp -f /var/lib/ntp/ntp.drift (code=exited, status=255)
 Main PID: 49622 (code=exited, status=255)

Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listen normally on 8 lo ::1 UDP 123
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listen normally on 9 eno2 fe80::e611:5bff:fe95:eff1 UDP 123
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listen normally on 10 eno1 fe80::e611:5bff:fe95:eff0 UDP 123
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listen normally on 11 veth85c1 fe80::5c81:4eff:fe09:1e13 UDP 123
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listen normally on 12 veth5935 fe80::8418:8ff:fe5b:78dd UDP 123
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listen normally on 13 vethb09f fe80::948a:55ff:fea7:39fc UDP 123
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: peers refreshed
Nov 10 12:24:56 tc-tac01.test.ise.com ntpd[49622]: Listening on routing socket on fd #30 for interface updates
Nov 10 12:29:20 tc-tac01.test.ise.com systemd[1]: ntpd.service: main process exited, code=exited, status=255/n/a
Nov 10 12:29:20 tc-tac01.test.ise.com systemd[1]: Unit ntpd.service entered failed state.

core@tc-tac01 ~ $ sudo systemctl start ntpd.service

core@tc-tac01 ~ $ sudo systemctl status ntpd.service
● ntpd.service - Network Time Service
   Loaded: loaded (/usr/lib64/systemd/system/ntpd.service; disabled)
   Active: active (running) since Sun 2014-12-07 20:37:11 UTC; 3s ago
 Main PID: 8828 (ntpd)
   CGroup: /system.slice/ntpd.service
           └─8828 /usr/sbin/ntpd -g -n -u ntp:ntp -f /var/lib/ntp/ntp.drift

Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 7 lo ::1 UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 8 eno2 fe80::e611:5bff:fe95:eff1 UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 9 eno1 fe80::e611:5bff:fe95:eff0 UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 10 veth2522 fe80::5493:cdff:fe68:4c1e UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 11 veth50b4 fe80::10c8:e7ff:fe3b:b94e UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 12 veth60a4 fe80::9c6b:7fff:fe7d:5c43 UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 13 vethb905 fe80::3cab:68ff:fe0e:1875 UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listen normally on 14 veth7338 fe80::2844:82ff:fea2:2e2 UDP 123
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: peers refreshed
Dec 07 20:37:11 tc-tac01.test.ise.com ntpd[8828]: Listening on routing socket on fd #31 for interface updates

core@tc-tac01 ~ $ date
Sun Dec  7 20:38:16 UTC 2014
```
Now its up, but its time is off. How do I sync it?