day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit CacheGcDaily Directive Description: The recurring time each day for garbage collection to be run. (24 hour clock) Syntax: CacheGcDaily time Default: CacheGcDaily ? Context: server config, virtual host Status: Experimental should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) • The machines’ times are synchronized via NTP or other network time protocol. • The

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines' to happen). Suppose that time repeats itself for some reason. That is, suppose that the system's clock is screwed up and it revisits a past time (or it is too far forward, is reset correctly, and then

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines' to happen). Suppose that time repeats itself for some reason. That is, suppose that the system's clock is screwed up and it revisits a past time (or it is too far forward, is reset correctly, and then

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines' to happen). Suppose that time repeats itself for some reason. That is, suppose that the system's clock is screwed up and it revisits a past time (or it is too far forward, is reset correctly, and then

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines' to happen). Suppose that time repeats itself for some reason. That is, suppose that the system's clock is screwed up and it revisits a past time (or it is too far forward, is reset correctly, and then

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines' to happen). Suppose that time repeats itself for some reason. That is, suppose that the system's clock is screwed up and it revisits a past time (or it is too far forward, is reset correctly, and then

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) • The machines’ times are synchronized via NTP or other network time protocol. • The to happen). Suppose that time repeats itself for some reason. That is, suppose that the system’s clock is screwed up and it revisits a past time (or it is too far forward, is reset correctly, and then

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit r:puts("Server 1's thread 1 has thread ID " .. thread.tid .. " and is in " .. thread.status .. " status") r:clock() -- Returns the current time with microsecond precision r:requestbody(filename) -- Reads and returns should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines'

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit r:puts("Server 1's thread 1 has thread ID " .. thread.tid .. " and is in " .. thread.status .. " status") r:clock() -- Returns the current time with microsecond precision r:requestbody(filename) -- Reads and returns should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines'

day of month %H 2-digit hour (24 hour clock) %I 2-digit hour (12 hour clock) %j 3-digit day of year %M 2-digit minute %m 2-digit month %p am/pm of 12 hour clock (localized) %S 2-digit second %U 2-digit r:puts("Server 1's thread 1 has thread ID " .. thread.tid .. " and is in " .. thread.status .. " status") r:clock() -- Returns the current time with microsecond precision r:requestbody(filename) -- Reads and returns should satisfy these requirements. (Even if you have only one machine you should synchronize its clock with NTP.) The machines' times are synchronized via NTP or other network time protocol. The machines'