Expire On - This option lets you set an expiration date for the script. The script will not run on and after the specified date and display the following error message: "This script has expired".

Expire in XX Days - This option lets you set an expiration date in days since today. The script will not run after XX days from today and display the following error message: "This script has expired" (Hours, mins and seconds not yet supported).

Time Servers (Optional - Using atomic clock servers for expiration date checking If you use a time lock option for your scripts you may wish to let the script check time with online time service rather than using local time on the server where your protected script is running. You may specify a list of time services by comma delimiting them.

Protocols supported for time checking:

- 'time' protocol (tcp to port 37)
- 'NTP' protocol (udp to port 123)

If you are using a time-server option when encoding your files, they will *require* the Internet connection in order to run. Time servers will be checked in the specified order. If all servers from the specified list are offline when the protected script is running then an error message will be displayed and the script terminates:

"This protected script requires the Internet connection in order to run [20]"

Source Guardian Command Line Reference:
--expiry
--days (obsolete in 11.3)
--time-server