diff options
| author | Joker <mac-joker@users.noreply.github.com> | 2014-11-17 10:42:15 +0100 |
|---|---|---|
| committer | Joker <mac-joker@users.noreply.github.com> | 2014-11-17 10:42:15 +0100 |
| commit | 75896bdd32c7223ea0a0cf5b1dabdf216fbf277a (patch) | |
| tree | 49eb432fa872c46a52191e1ab23efeb6695b4fb0 /README | |
| parent | 6c207c9c6886033980e78d48493bbf522da4b964 (diff) | |
| download | libfaketime-75896bdd32c7223ea0a0cf5b1dabdf216fbf277a.tar.gz | |
added runtime cache manipulation: change duration and active state with environment variables
Diffstat (limited to 'README')
| -rw-r--r-- | README | 10 |
1 files changed, 6 insertions, 4 deletions
@@ -315,12 +315,14 @@ Using relative offsets or 'start at' dates solves this problem. libfaketime then will always report the faked time based on the real current time and the offset you've specified. -Please also note that your specification of the fake time is cached for 10 -seconds in order to enhance the library's performance. Thus, if you change the +Please also note that your default specification of the fake time is cached for +10 seconds in order to enhance the library's performance. Thus, if you change the content of $HOME/.faketimerc or /etc/faketimerc while a program is running, it may take up to 10 seconds before the new fake time is applied. If this is a -problem in your scenario, you can disable caching at compile time by adding the -command line option -DNO_CACHING to this library's Makefile. +problem in your scenario, you can change number of seconds before the file is read +again with environment variable FAKETIME_CACHE_DURATION, or disable caching at all +with FAKETIME_NO_CACHE=1. Remember that disabling the cache may negatively +influence the performance. 4f) Faking the date and time system-wide |