Here's what I did on a Ubuntu EC2:
A) Login as root using the keypairs
B) Setup the necessary users and their passwords with
$ sudo adduser USERNAME
$ sudo passwd USERNAME
| # =====================[ EXPIRES CACHING ]===================== | |
| <IfModule mod_expires.c> | |
| ExpiresActive On | |
| ExpiresByType image/jpg "access 1 year" | |
| ExpiresByType image/jpeg "access 1 year" | |
| ExpiresByType image/gif "access 1 year" | |
| ExpiresByType image/png "access 1 year" | |
| ExpiresByType text/css "access 1 month" | |
| ExpiresByType text/html "access 1 month" | |
| ExpiresByType application/pdf "access 1 month" |
Here's what I did on a Ubuntu EC2:
A) Login as root using the keypairs
B) Setup the necessary users and their passwords with
$ sudo adduser USERNAME
$ sudo passwd USERNAME
To edit or create your own crontab file, type the following command at the UNIX / Linux shell prompt:
$ crontab -e
No. Cron will examine the modification time on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab file is modified.
The syntax is:
How to fix warning about ECDSA host key
Remove the cached key for IP/DNS on the local machine:
ssh-keygen -R IP/DNS