099d982c2b0803a35b4f6be3cae3e65b3cd86fa3
wiki/creating-ec2-image-from-scratch.md
| ... | ... | @@ -87,4 +87,12 @@ Copied /etc/logrotate.conf from an existing SL instance so that `/var/log/logrot |
| 87 | 87 | |
| 88 | 88 | Instead of having the `ANDROID_HOME` environment variable be set in `/etc/profile` as in the old instances, I moved this statement to the `sailing.sh` script in git at `configuration/sailing.sh` and linked to by `/etc/profile.d/sailing.sh`. For old instances this will set the variable redundantly, as they also have it set by a manually adjusted `/etc/profile`, but this shouldn't hurt. |
| 89 | 89 | |
| 90 | -Had to fiddle a little with the JDK being used. The default installation has an OpenJDK installed, and the AWS tools depend on it. Therefore, it cannot just be removed. As a result, it's important that `env.sh` has the correct `JAVA_HOME` set (/opt/jdk1.8.0_45, in this case). Otherwise, the OSGi environment won't properly start up. |
|
| ... | ... | \ No newline at end of file |
| 0 | +Had to fiddle a little with the JDK being used. The default installation has an OpenJDK installed, and the AWS tools depend on it. Therefore, it cannot just be removed. As a result, it's important that `env.sh` has the correct `JAVA_HOME` set (/opt/jdk1.8.0_45, in this case). Otherwise, the OSGi environment won't properly start up. |
|
| 1 | + |
|
| 2 | +To ensure that chronyd is started during the boot sequence, issued the command |
|
| 3 | + |
|
| 4 | +``` |
|
| 5 | +chkconfig chrony on |
|
| 6 | +``` |
|
| 7 | + |
|
| 8 | +which creates the necessary entries in the rc*.d directories. |
|
| ... | ... | \ No newline at end of file |