rms/libfaketime
1
0
Fork 0
mirror of https://github.com/wolfcw/libfaketime.git synced 2026-05-17 00:26:16 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merged master in and cleaned up.

Browse Source 
We no longer need the OSX-specific test. Tests are passing, too.
This commit is contained in:
Michael D. Stemle, Jr
2019-11-27 14:32:15 -05:00
parent 150a6cb3b2 826f8b7792
commit f92d919fb0
29 changed files with 1022 additions and 555 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

@@ -7,3 +7,5 @@ src/libfaketime.1.dylib
src/core
src/faketime
m4/*.m4*
.vscode/

11
.travis.yml Normal file
View File

@@ -0,0 +1,11 @@
language: c
matrix:
include:
- os: linux
compiler: gcc
script:
- cd ${TRAVIS_BUILD_DIR}
- FAKETIME_COMPILE_CFLAGS="-DFORCE_MONOTONIC_FIX" make
- make test

38
NEWS
View File

@@ -1,6 +1,42 @@
Since 0.9.7:
Since 0.9.9:
- Mike Stemle added GNU autotools
Since 0.9.8:
- Compile-time CFLAG FAKE_SETTIME can be enabled to
intercept calls to clock_settime(), settimeofday(), and
adjtime(). (suggested and prototyped by @ojura)
- Additional compile-time CFLAGs can be passed via the
environment variable FAKETIME_COMPILE_CFLAGS when
running 'make'.
- src/Makefile CFLAG FORCE_PTHREAD_NONVER should be set on
systems that hang on CLOCK_REALTIME, or that hang on
CLOCK_MONOTONIC where FORCE_MONOTONIC_FIX is not sufficient.
Since 0.9.7:
- Passthrough for unknown clock ids to avoid error messages
- Fixes for multithreaded operations (mliertzer, qnox)
- glibc-related fixes (jprjr) and gcc8 support (tpetazzoni)
- Improved error message output on parsing errors
- fix file stat() faking when 'i' modifier is used for determinism
- Use FAKETIME="%" to take FAKETIME setting from a file as
specified in FAKETIME_FOLLOW_FILE
- Added FAKETIME_DONT_RESET environment variable to avoid
faketime resets when subprocesses are started (similar to
the old v0.9.6 behavior)
- Added FAKETIME_XRESET to avoid large clock jumps when
the 'x' modifier is used and changed during run-time
- Do not fake time during libfaketime initialization to
improve compatibility with memory allocation libraries that
use time-related functions themselves
- Fixes for shared memory related issues, especially when
not using the faketime wrapper
- Updated glibc compatibility settings for various platforms
- Support for clock_nanosleep() with realtime and monotonic clocks
- Support for epoll_wait(), epoll_pwait(), and pselect()
- src/Makefile CFLAG FORCE_MONOTONIC_FIX should be set (only) on
platforms where the test program hangs forever at the
CLOCK_MONOTONIC test.
Since 0.9.6:
- Julien Gilli added an option to disable monotonic time faking
- Azat Khuzhin added support for COARSE clocks

150
README
View File

@@ -1,5 +1,5 @@
libfaketime, version 0.9.7 (November 2017)
==========================================
libfaketime, version 0.9.8 (August 2019)
========================================
Content of this file:
@@ -71,18 +71,37 @@ documentation whether it can be achieved by using libfaketime directly.
rebuilding libfaketimeMT.so.1
* Java-/JVM-based applications work but you need to pass in an extra argument
(DONT_FAKE_MONOTONIC). See usage basics below for details. Without this
argument the java command usually hangs.
(FAKETIME_DONT_FAKE_MONOTONIC). See usage basics below for details. Without
this argument the java command usually hangs.
* libfaketime will eventually be bypassed by applications that dynamically load
system libraries, such as librt, explicitly themselves instead of relying on
the linker to do so at application start time. libfaketime will not work with
those applications unless you can modify them.
This apparently happens a lot in complex run-time environments, e.g., for
programs written in golang, for some Java Virtual Machine implementations,
etc. Since libfaketime is effectively bypassed in such situations, there's
nothing we can do about it. Please consider asking the appropriate developers
and vendors to implement their runtime environment in a way that supports
intercepting selected system calls through LD_PRELOAD.
* Applications can explicitly be designed to prevent libfaketime from working,
e.g., by checking whether certain environment variables are set or whether
libfaketime-specific files are present.
* CLOCK_MONOTONIC test: Running "make test" performs a series of tests after
successful compilation of the libfaketime library. On some platforms, the
"CLOCK_MONOTONIC test" will apparently hang forever. If and only if this
happens on your platform, add the CFLAG -DFORCE_MONOTONIC_FIX to
src/Makefile and recompile libfaketime. Do not set FORCE_MONOTONIC_FIX on
platforms where the test does not hang.
If you observe hangs on the CLOCK_REALTIME test, add the CFLAG
-DFORCE_PTHREAD_NONVER. Also set this FORCE_PTHREAD_NONVER flag in case
FORCE_MONOTONIC_FIX alone does not solve the hang on the MONOTONIC_CLOCK
test.
3. Installation
---------------
@@ -151,7 +170,7 @@ user@host> LD_PRELOAD=/usr/local/lib/libfaketime.so.1 FAKETIME="-15d" date
Mon Nov 8 12:01:12 CEST 2016
user@host> LD_PRELOAD=/usr/local/lib/libfaketime.so.1 FAKETIME="-15d"
DONT_FAKE_MONOTONIC=1 java -version
FAKETIME_DONT_FAKE_MONOTONIC=1 java -version
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
@@ -215,6 +234,22 @@ specified absolute time. The 'start at' format allows a 'relative' clock
operation as described below in section 4d), but using a 'start at' time
instead of an offset time.
If the started process itself starts other (child) processes, they by default
will start with the specified start-at-date again. If this is not what you need,
set the environment variable FAKETIME_DONT_RESET=1. Try these examples to see
the difference:
LD_PRELOAD=src/libfaketime.so.1 FAKETIME="@2000-01-01 11:12:13" \
FAKETIME_DONT_RESET=1 \
/bin/bash -c 'while [ $SECONDS -lt 5 ]; do date; sleep 1; done'
LD_PRELOAD=src/libfaketime.so.1 FAKETIME="@2000-01-01 11:12:13" \
/bin/bash -c 'while [ $SECONDS -lt 5 ]; do date; sleep 1; done'
In the second example, the "date" command will always print the same time,
while in the first example, with FAKETIME_DONT_RESET set, time will increment
even though all the "date" commands are new processes.
4d) Using offsets for relative dates
------------------------------------
@@ -234,6 +269,11 @@ optionally followed by a multiplier:
export FAKETIME="-10m" sets the faked time 10 minutes behind the real time.
export FAKETIME="+14d" sets the faked time to 14 days in the future.
Please note that if you need other multipliers (weeks, months etc.) or higher
precision (e.g., correct leap year handling), you should use either the
faketime wrapper or the GNU date command as shown in the first of the three
examples below.
You now should understand the complete example we've used before:
LD_PRELOAD=/usr/local/lib/libfaketime.so.1 FAKETIME="-15d" date
@@ -291,6 +331,11 @@ completely independently of the system clock. It helps running programs
with some determinism. In this single case all spawned processes will use
the same global clock without restarting it at the start of each process.
Please note that using "x" or "i" in FAKETIME still requires giving an offset
(see section 4d). This means that "+1y x2" will work, but "x2" only will not.
If you do not want to fake the time, but just modify clock speed, use something
like "+0 x2", i.e., use an explizit zero offset as a prefix in your FAKETIME.
For testing, your should run a command like
LD_PRELOAD=./libfaketime.so.1 FAKETIME="+1,5y x10,0" \
@@ -336,6 +381,101 @@ with FAKETIME_NO_CACHE=1. Remember that disabling the cache may negatively
influence the performance.
Setting FAKETIME by means of a file timestamp
---------------------------------------------
Based on a proposal by Hitoshi Harada (umitanuki), the "start at" time can now be
set through any file in the file system by setting the FAKETIME environment variable
to "%" (a percent sign) and FAKETIME_FOLLOW_FILE to the name of the file whose
modification timestamp shall be used as source for the "start at" time.
Usage example:
# create any file with December 24th, 2009, 12:34:56 as timestamp
touch -t 0912241234.56 /tmp/my-demo-file.tmp
# run a bash shell with an endless loop printing the current time
LD_PRELOAD=/path/to/libfaketime.so.1 \
FAKETIME='%' FAKETIME_FOLLOW_FILE=/tmp/my-demo-file.tmp \
FAKETIME_DONT_RESET=1 \
bash -c 'while true ; do date ; sleep 1 ; done'
# now, while the above is running, change the file's timestamp
# (in a different terminal window or whatever)
touch -t 2002290123.45 /tmp/my-demo-file.tmp
Changing the 'x' modifier during run-time
-----------------------------------------
Using FAKETIME_TIMESTAMP_FILE allows for easily changing the FAKETIME setting
while a program is running:
echo "+0 x1" > /tmp/my-faketime.rc
LD_PRELOAD=libfaketime.so.1 FAKETIME_TIMESTAMP_FILE="/tmp/my-faketime.rc" \
FAKETIME_NO_CACHE=1 ./some-program &
sleep 10 ; echo "+0 x10" > /tmp/my-faketime.rc
Changing the speed of the wall clock time, i.e., using a different 'x' modifier
during run-time, by default can lead to greater jumps that may confuse the
program. For example, if the program has been running for 10 seconds on 'x1',
and then the setting is changed to 'x10', the faked time will look to the
program as if it has been running for more than 100 instead of just more than
10 seconds.
By setting the environment variable FAKETIME_XRESET to any value, transitions
between different 'x' modifier values will be significantly smoothed:
LD_PRELOAD=libfaketime.so.1 FAKETIME_TIMESTAMP_FILE="/tmp/my-faketime.rc" \
FAKETIME_NO_CACHE=1 FAKETIME_XRESET=1 ./some-program &
Setting FAKETIME_XRESET ensures that wall clock time begins to run faster
only after the 'x' modifier has been changed (when increasing it) and also
ensures that the reported faked time does not jump back to past values
(when decreasing it).
Please note that FAKETIME_XRESET internally works by resetting libfaketime's
internal time-keeping data structures, which may have side effects on reported
file timestamps. Using FAKETIME_XRESET should be considered experimental at
the moment.
Cleaning up shared memory
-------------------------
libfaketime uses semaphores and shared memory on platforms that support it in
order to sync faketime settings across parent-child processes. It will clean
up when it exits properly. However, when processes are terminated (e.g., by
Ctrl-C on command line), shared memory cannot be cleaned up properly. In such
cases, you should occasionally delete
/dev/shm/faketime_shm_* and
/dev/shm/sem.faketime_sem_*
manually (or properly automated). Leftover files there from processes that
already have been terminated are not a problem in general, but result in a
libfaketime error the next time a process is started with a process id for
which such a stale semaphore/shared memory exists. Thus, if you run across
the following error message
libfaketime: In ft_shm_create(), shm_open failed: File exists
please cleanup /dev/shm as described above. This is especially relevant
for long-running systems (servers with high uptime) and systems on which
a lot of processes are started (e.g., servers handling many containers
or similar virtualization mechanisms).
Intercepting time-setting calls
-------------------------------
libfaketime can be compiled with the CFLAG "-DFAKE_SETTIME" in order
to also intercept time-setting functions, i.e., clock_settime(),
settimeofday(), and adjtime(). Instead of passing the timestamp a
program sets through to the system, only the FAKETIME environment
variable will be adjusted accordingly.
4f) Faking the date and time system-wide
----------------------------------------

40
README.OSX
View File

@@ -5,16 +5,14 @@ Support for macOS has meanwhile matured and many command line and
GUI applications will run stable.
Developments and tests are done on Mojave currently.
Use libfaketime 0.9.6 or earlier on OS X (i.e., before Sierra).
Version 0.9.5 and higher no longer works with OSX <= 10.6 due to
Version 0.9.5 and higher no longer work with OSX <= 10.6 due to
changes in the underlying system libraries. If you need libfaketime
on OSX <= 10.6, please use libfaketime version 0.9.
Installing and using libfaketime on OS X is slightly different than
Installing and using libfaketime on macOS is slightly different than
on Linux. Please make sure to read the README file for general
setup and usage, and refer to this file only about OS X specifics.
setup and usage, and refer to this file only about macOS specifics.
1) Installing libfaketime on macOS
@@ -33,6 +31,10 @@ Or, if you use Homebrew, install using:
brew install libfaketime
Please inform the respective package maintainers if the latest release
is not yet available this way. With homebrew, you can typically use
"brew install --HEAD" to install from the latest source automatically.
Otherwise, you have to compile and install libfaketime manually; this
will require a working installation of Xcode and its command line tools
on your machine.
@@ -60,7 +62,7 @@ system-dependent files by running:
---------------------------------------------------
You will need to set three environment variables. In a Terminal.app
or iTerm2 session, the following commands can be used:
or any other CLI session, the following commands can be used:
export DYLD_FORCE_FLAT_NAMESPACE=1
export DYLD_INSERT_LIBRARIES=/path/to/libfaketime.1.dylib
@@ -81,7 +83,7 @@ for help and use "man faketime" for details.
--------------------------------------------
Given the limited number of system calls libfaketime intercepts,
it may not work too well with specific GUI applications on OS X.
it may not work too well with specific GUI applications on macOS.
This can result in crashes after a seemingly random time, or an
application will not or at least not always see the faked time,
and so on.
@@ -132,13 +134,20 @@ time-related system calls that need to be intercepted on macOS.
https://github.com/wolfcw/libfaketime/issues
Important: When reporting non-working applications, please make
sure that your issue is not related to SIP (system integrity
protection). For example, on a SIP-enabled, default macOS installation,
libfaketime will not work for programs like /bin/bash because
the path /bin is SIP-protected. Copy your application to a
non-SIP-protected path, and if libfaketime still does not work,
feel free to report it.
However, there are two important aspects:
- When reporting non-working applications, please make sure that your issue is
not related to SIP (system integrity protection). For example, on a
SIP-enabled, default macOS installation, libfaketime will not work for
programs like /bin/bash because the path /bin is SIP-protected. Copy your
application to a non-SIP-protected path, and if libfaketime still does not
work, feel free to report it.
- We cannot and will not help with using libfaketime for proprietary or
commercial software unless you are its developer trying to integrate
libfaketime. Please contact the developers or the vendor directly if
you have problems using libfaketime with non-free / not open sourced
macOS applications.
4) Notes for developers of macOS applications
@@ -146,4 +155,5 @@ feel free to report it.
The environment variable FAKETIME can be changed at application run-time
and always takes precedence over other user-controlled settings. It can
be re-set to 0 (zero) to work around potential incompatibilities.
be re-set to 0 (zero) to work around potential incompatibilities or if
you do not want libfaketime applied to your software.

47
README.developers
View File

@@ -4,20 +4,27 @@ This file contains information for libfaketime developers and contributors.
GENERAL
=======
Starting with libfaketime v0.9.5, development and issue handling is
completely done via Github:
Starting with libfaketime v0.9.5, development and issue handling is
completely done via Github:
https://github.com/wolfcw/libfaketime
- Official releases are tagged.
- Code contributions and bugfixes are merged into the "development" branch,
which is considered unstable and may contain code that is not yet fully
tested.
- Official releases are tagged.
- Code contributions and bugfixes should be submitted to and then merged into
the "development" branch, which is considered unstable and may contain code
that is not yet fully tested.
- The "master" branch is updated with tested code only; it is ensured that
it compiles and works cleanly at least on current Linux and OS X systems.
it compiles and works cleanly at least on current Linux and macOS systems.
Code contributions are highly welcome, preferably via pull requests on Github.
Please have a look at issues labelled as "help wanted" in the Github issue
tracker. If you are interested in contributing to libfaketime, helping with
these issues is not only much appreciated, but also a good way to familiarize
yourself with the overall codebase.
CODE STYLE
==========
@@ -43,16 +50,16 @@ void do_nothing(int how_often)
}
}
- Use -DDEBUG and #ifdef DEBUG for development and testing. Avoid printing
to stdout or stderr outside "#ifdef DEBUG"; if it is necessary to inform
the user a run-time, prefix your output with "faketime" or make otherwise
sure that the user knows where the message is coming from.
- Use -DDEBUG and #ifdef DEBUG for development and testing. Avoid printing to
stdout or stderr outside "#ifdef DEBUG"; if it is necessary to inform the
user a run-time, prefix your output with "libfaketime" or make otherwise sure
that the user knows where the message is coming from.
- If you add new functions to libfaketime.c, try placing them somewhere
where they fit will: Usually, functions are grouped by functionality
(e.g., all functions related to faking file timestamps). If that's not
possible, group them by contributor, or document your placement strategy
in the commit message.
in the commit message.
DEVELOPMENT, BUILDING, AND TESTING
@@ -62,19 +69,19 @@ DEVELOPMENT, BUILDING, AND TESTING
the modification fixes bugs :-)).
- Add tests for new features. Extend test/timetest.c appropriately and
try to use the functional testing framework wherever possible.
try to use the functional testing framework wherever possible.
- Compiler and linker warnings are treated as errors and not acceptable.
- If you cannot test the code on both Linux and OS X yourself, please
let us know and consider wrapping your code in #ifdef / #ifndef __APPLE__
statements.
- If you cannot test the code on both Linux and macOS yourself, please
let us know and consider wrapping your code in #ifdef / #ifndef __APPLE__
statements.
DOCUMENTATION
=============
For anything more than small bugfixes, please update the user documentation
For anything more than small bugfixes, please update the user documentation
and credits appropriately:
- The NEWS file should mention the change and your credits.
@@ -83,8 +90,8 @@ and credits appropriately:
- The manpage man/faketime.1 should be updated when the wrapper application
is modified.
For credits, please either mention your real name, your Github username, or
your email address.
For credits, please either mention your real name, your Github username, or
your email address.
In your own interest, please be verbose on user documentation and comments
in the source code. Users will not know about new features unless they are
@@ -97,7 +104,7 @@ RELEASES
Official new releases are created whenever a significant amount of changes
(bugfixes or new functionality) has piled up; on average, there is one new
official release per year. Users who need to stick to the bleeding edge
official release per 1-2 years. Users who need to stick to the bleeding edge
are supposed to use the current state of the "master" branch at any time.
libfaketime maintainers for several Linux distributions are informed about

62
README.packagers Normal file
View File

@@ -0,0 +1,62 @@
README for packagers of libfaketime
First, thank you for your efforts to make libfaketime packages available
on your platform / distribution!
libfaketime has tagged releases about once every 1-2 years, made available
through github.com/wolfcw/libfaketime, but usually it is also safe (i.e.,
stable) to use the latest HEAD of the master branch, which contains bug
fixes since the last tagged release.
You may want to familiarize yourself with the options you can set into
src/Makefile, but sane defaults for stable operations have been chosen.
Currently, libfaketime does not use autotools yet, so there is
_no_ ./configure step, but "make" and "make test" will work as expected.
However, one problem makes it somewhat difficult to get libfaketime
working on different platforms:
libfaketime currently has the challenge that depending on the version
of glibc and the platform (e.g., x86_64 or aarch64) certain compiler
CFLAGS have to be set manually, as we have not yet found a way to
safely determine behavior at run-time automatically.
Please proceed as follows:
- run "make test". If everything runs through smoothly and you do not
encounter any hangs or test failure reports, use the binaries as
they are.
- If you encounter endless hangs during the CLOCK_REALTIME test,
add -DFORCE_PTHREAD_NONVER to the CFLAGS.
- If you encounter endless hangs during the CLOCK_MONOTONIC test,
add -DFORCE_MONOTONIC_FIX to the CFLAGS. If it works with that,
it's fine, otherwise additionally use -DFORCE_PTHREAD_NONVER.
CFLAGS can also be passed through the FAKETIME_COMPILE_CFLAGS environment
variable, so for example
FAKETIME_COMPILE_CFLAGS="-DFORCE_PTHREAD_NONVER" make test
would create the libfaketime binaries and run the tests with the
FORCE_PTHREAD_NONVER flag set in a single step.
Please do not use FORCE_MONOTONIC_FIX by default, as it would result
in incorrect operations on platforms that do not need it.
Our observations with a limited number of Linux distributions is that
libfaketime may require different compile flags per platform even
if the same distribution and glibc version is used across these
platforms.
As soon as we have found a reliable way to automatically choose the
correct compile-time flags, we will remove this burden from you as
packager for obvious reasons. Until then, please feel free to report
your experiences with different platforms and distribution versions
through the issue tracker on Github.
Again, thanks for your time and effort to make libfaketime available
easily for everyone else!

19
TODO
View File

@@ -1,8 +1,15 @@
Open issues / next steps for libfaketime development
Open issues / next steps for libfaketime development:
Please see the issue tracker on Github - https://github.com/wolfcw/libfaketime
- New features, such as additional system calls to intercept, are labelled
"feature request" when they are considered for implementation
- Issues labelled "help wanted" should be your starting point if you are
interested in contributing to libfaketime
Besides the open issues, two major changes are planned for the next release:
- integrate manchicken's autoconf/automake support to get rid of separate Makefile.OSX
- add more functional tests that check more than the basic functionality
- add unit tests specifically for the faketime program
- use the testing framework to also implement unit tests
- fake timer_create and friends
- work around thread local storage issue, e.g., by using pthreads
- improve pthread support

2
man/faketime.1
View File

@@ -1,4 +1,4 @@
.TH FAKETIME "1" "November 2017" "faketime 0.9.7" wolfcw
.TH FAKETIME "1" "August 2019" "faketime 0.9.8" wolfcw
.SH NAME
faketime \- manipulate the system time for a given command
.SH SYNOPSIS

25
packaging/Linux/Arch/PKGBUILD-32bit.txt
View File

@@ -1,25 +0,0 @@
# Maintainer: Robert Orzanna <orschiro@gmail.com>
_pkgbasename=libfaketime
pkgname=lib32-$_pkgbasename
pkgver=0.9.5
pkgrel=1
pkgdesc='Report fake dates and times to programs without having to change the system-wide time.'
arch=('x86_64')
url='http://www.code-wizards.com/projects/libfaketime/'
license=('GPL2')
source=("http://www.code-wizards.com/projects/${_pkgbasename}/${_pkgbasename}-${pkgver}.tar.gz"
'lib32.patch')
md5sums=('89b5c71e6c6a93b1c6feba374ac37719'
'0a01f842df4c8acbd2b081be046e8d67')
build() {
cd "${_pkgbasename}-${pkgver}"
patch -p1 -i ../lib32.patch
make
}
package() {
cd "${_pkgbasename}-${pkgver}"
make PREFIX=/usr DESTDIR="${pkgdir}" install
}

30
packaging/Linux/Debian/avoid-spurious-lrt.patch
View File

@@ -1,30 +0,0 @@
Author: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
On i386 systems, for some reason if i do not clean up this extra -lrt, i get the following error:
[...]
make[1]: Entering directory `/home/dkg/src/faketime/faketime/src'
cc -o libfaketime.o -c -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=gnu99 -Wall -Wextra -Werror -DFAKE_STAT -DFAKE_SLEEP -DFAKE_TIMERS -DFAKE_INTERNAL_CALLS -fPIC -DPREFIX='"'/usr/local'"' -DLIBDIRNAME='"'/lib/faketime'"' -DMULTI_ARCH libfaketime.c
cc -o libfaketime.so.1 -Wl,-soname,libfaketime.so.1 -Wl,-z,relro -Wl,--version-script=libfaketime.map -lrt -shared libfaketime.o -ldl -lm -lpthread -lrt
libfaketime.o: In function `ft_cleanup':
/home/dkg/src/faketime/faketime/src/libfaketime.c:1277: multiple definition of `timer_gettime'
/home/dkg/src/faketime/faketime/src/libfaketime.c:1277: multiple definition of `timer_settime'
collect2: error: ld returned 1 exit status
make[1]: *** [libfaketime.so.1] Error 1
[...]
I confess i don't really understand why removing this would fix
things, but i also don't see the need to have multiple attempts to
link to librt.
--- a/src/Makefile
+++ b/src/Makefile
@@ -69,7 +69,7 @@
CFLAGS += -std=gnu99 -Wall -Wextra -Werror -DFAKE_STAT -DFAKE_SLEEP -DFAKE_TIMERS -DFAKE_INTERNAL_CALLS -fPIC -DPREFIX='"'$(PREFIX)'"' -DLIBDIRNAME='"'$(LIBDIRNAME)'"'
LIB_LDFLAGS += -shared
-LDFLAGS += -Wl,--version-script=libfaketime.map -lrt
+LDFLAGS += -Wl,--version-script=libfaketime.map
LDADD += -ldl -lm -lpthread -lrt
SRC = libfaketime.c

40
packaging/Linux/Debian/control
View File

@@ -1,40 +0,0 @@
Source: faketime
Section: utils
Priority: extra
Maintainer: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Build-Depends:
debhelper (>= 9),
dh-exec (>= 0.3)
Standards-Version: 3.9.4
Homepage: http://www.code-wizards.com/projects/libfaketime/
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/faketime.git
Vcs-Git: git://anonscm.debian.org/collab-maint/faketime.git
Package: faketime
Architecture: any
Pre-Depends: multiarch-support
Depends: ${shlibs:Depends}, ${misc:Depends}, libfaketime (= ${binary:Version})
Multi-Arch: foreign
Description: report faked system time to programs
The Fake Time Preload Library (FTPL, a.k.a. libfaketime) intercepts
various system calls which programs use to retrieve the current date
and time. It can then report faked dates and times (as specified by
you, the user) to these programs. This means you can modify the
system time a program sees without having to change the time
system-wide. FTPL allows you to specify both absolute dates (e.g.,
2004-01-01) and relative dates (e.g., 10 days ago).
Package: libfaketime
Architecture: any
Pre-Depends: multiarch-support
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: report faked system time to programs
The Fake Time Preload Library (FTPL, a.k.a. libfaketime) intercepts
various system calls which programs use to retrieve the current date
and time. It can then report faked dates and times (as specified by
you, the user) to these programs. This means you can modify the
system time a program sees without having to change the time
system-wide. FTPL allows you to specify both absolute dates (e.g.,
2004-01-01) and relative dates (e.g., 10 days ago).

29
packaging/Linux/Debian/fix-infinite-recursion-on-real_clock_gettime.patch
View File

@@ -1,29 +0,0 @@
From: Gerardo Malazdrewicz <gerardo@malazdrewicz.com.ar>
To: 699559@bugs.debian.org
Subject: Avoiding loop (very dirty patch)
Date: Tue, 26 Mar 2013 01:18:05 +0100
[Message part 1 (text/plain, inline)]
Attached patch works for me, but it is very very dirty.
Possibly side effects.
Alternative seems to be to protect the call to real_clock_gettime so it is
executed just once (to validate the parameters). Subsequent calls are not
needed (parameters have been validated).
Thanks,
Gerardo
--- a/src/libfaketime.c
+++ b/src/libfaketime.c
@@ -1380,7 +1380,7 @@ void __attribute__ ((constructor)) ftpl_init(void)
real_clock_get_time = dlsym(RTLD_NEXT, "clock_get_time");
real_clock_gettime = apple_clock_gettime;
#else
- real_clock_gettime = dlsym(RTLD_NEXT, "clock_gettime");
+ real_clock_gettime = dlsym(RTLD_NEXT, "__clock_gettime");
#ifdef FAKE_TIMERS
real_timer_settime_22 = dlvsym(RTLD_NEXT, "timer_settime","GLIBC_2.2");
real_timer_settime_233 = dlvsym(RTLD_NEXT, "timer_settime","GLIBC_2.3.3");

3
packaging/Linux/Debian/libfaketime.install
View File

@@ -1,3 +0,0 @@
#!/usr/bin/dh-exec
src/libfaketime.so.1 usr/lib/${DEB_HOST_MULTIARCH}/faketime/
src/libfaketimeMT.so.1 usr/lib/${DEB_HOST_MULTIARCH}/faketime/

17
packaging/Linux/Debian/rules
View File

@@ -1,17 +0,0 @@
#!/usr/bin/make -f
# Author: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
# Date: Tue, 26 Aug 2008 14:24:50 -0400
export DEB_CFLAGS_MAINT_APPEND=-DMULTI_ARCH
# make sure dh_makeshlibs does not modify post{inst,rm} scripts:
# (avoids lintian's postinst-has-useless-call-to-ldconfig)
override_dh_makeshlibs:
dh_makeshlibs --noscripts
override_dh_installchangelogs:
dh_installchangelogs NEWS
%:
PREFIX=/usr dh $@

13
packaging/Linux/Redhat/libfaketime-fix-infinite-recursion-on-real_clock_gettime.patch
View File

@@ -1,13 +0,0 @@
diff --git a/src/libfaketime.c b/src/libfaketime.c
index 3ec372b..f70283b 100644
--- a/src/libfaketime.c
+++ b/src/libfaketime.c
@@ -1380,7 +1380,7 @@ void __attribute__ ((constructor)) ftpl_init(void)
real_clock_get_time = dlsym(RTLD_NEXT, "clock_get_time");
real_clock_gettime = apple_clock_gettime;
#else
- real_clock_gettime = dlsym(RTLD_NEXT, "clock_gettime");
+ real_clock_gettime = dlsym(RTLD_NEXT, "__clock_gettime");
#ifdef FAKE_TIMERS
real_timer_settime_22 = dlvsym(RTLD_NEXT, "timer_settime","GLIBC_2.2");
real_timer_settime_233 = dlvsym(RTLD_NEXT, "timer_settime","GLIBC_2.3.3");

55
packaging/Linux/Redhat/libfaketime.spec.txt
View File

@@ -1,55 +0,0 @@
Summary: Manipulate system time per process for testing purposes
Name: libfaketime
Version: 0.9.5
Release: 4%{?dist}
License: GPLv2+
Url: http://www.code-wizards.com/projects/%{name}/
Source: http://www.code-wizards.com/projects/%{name}/%{name}-%{version}.tar.gz
Group: System Environment/Libraries
Patch1: libfaketime-0.9.5-fix-infinite-recursion-on-real_clock_gettime.patch
%description
libfaketime intercepts various system calls which programs use to
retrieve the current date and time. It can then report faked dates and
times (as specified by you, the user) to these programs. This means you
can modify the system time a program sees without having to change the
time system- wide.
%prep
%setup -q
%patch1 -p1
# work around from upstream for autodetecting glibc version bug on i686
sed -i -e 's/__asm__(".symver timer_gettime_22/\/\/__asm__(".symver timer_gettime_22/' src/libfaketime.c
sed -i -e 's/__asm__(".symver timer_settime_22/\/\/__asm__(".symver timer_settime_22/' src/libfaketime.c
%build
cd src ; CFLAGS="$RPM_OPT_FLAGS -Wno-strict-aliasing" make %{?_smp_mflags} \
PREFIX="%{_prefix}" LIBDIRNAME="/%{_lib}/faketime" all
%check
make %{?_smp_mflags} -C test all
%install
make PREFIX="%{_prefix}" DESTDIR=%{buildroot} LIBDIRNAME="/%{_lib}/faketime" install
rm -r %{buildroot}/%{_docdir}/faketime
%files
%{_bindir}/faketime
%{_libdir}/faketime/libfaketime*so.*
%doc README COPYING NEWS README README.developers
%{_mandir}/man1/*
%changelog
* Tue Oct 15 2013 Paul Wouters <pwouters@redhat.com> - 0.9.5-4
- Infinite recursion patch is still needed, make test causes
segfaults otherwise.
* Mon Oct 14 2013 Paul Wouters <pwouters@redhat.com> - 0.9.5-3
- Work around from upstream for autodetecting glibc version bug on i686
* Mon Oct 14 2013 Paul Wouters <pwouters@redhat.com> - 0.9.5-2
- Remove use of ifarch for _lib macro for multilib
* Sun Oct 13 2013 Paul Wouters <pwouters@redhat.com> - 0.9.5-1
- Initial package

53
packaging/OSX/Fink/libfaketime.info
View File

@@ -1,53 +0,0 @@
Package: libfaketime
Version: 0.9.7
Revision: 1
Source: http://www.code-wizards.com/projects/%n/%n-%v.tar.gz
Source-MD5: 8617e2c6caf0977b3ce9a271f867302c
Maintainer: Wolfgang Hommel <wolf@fink.code-wizards.com>
HomePage: https://github.com/wolfcw/libfaketime
License: GPL
Description: Modify system time for single applications
DescDetail: <<
libfaketime is a library that is dynamically linked to applications
or system commands at run-time by using the DYLD_INSERT_LIBRARIES
mechanism. It then intercepts various system calls, which programs
use to retrieve the current date and time. libfaketime can then
report faked dates and times to these programs. This means you can
modify the system time a program uses without having to change the
date and time system-wide.
<<
DescUsage: <<
libfaketime includes a simple wrapper called faketime. Run the
command faketime without any parameters for usage information.
For information on how to use libfaketime without the wrapper
and access its full raw functionality, please see
%p/share/doc/libfaketime/README*
<<
BuildDepends: fink (>= 0.28)
Distribution: 10.7, 10.8, 10.9, 10.10, 10.11, 10.12
CompileScript: <<
#! /bin/sh -ev
make -f Makefile.OSX -C src PREFIX=%{p}
<<
InfoTest: <<
TestScript: make -f Makefile.OSX test || exit 2
<<
InstallScript: <<
#! /bin/sh -ev
make -f Makefile.OSX -C src install PREFIX=%{i}
<<
DocFiles: COPYING README README.OSX
Shlibs: <<
!%p/lib/faketime/%N.1.dylib
<<

21
packaging/OSX/Homebrew/libfaketime.rb
View File

@@ -1,21 +0,0 @@
require 'formula'
class Libfaketime < Formula
homepage 'https://github.com/wolfcw/libfaketime'
url 'https://github.com/wolfcw/libfaketime/archive/v0.9.7.tar.gz'
sha1 'eb1cbacf548aefa36214bea1345f35b8763027a1'
depends_on :macos => :sierra
fails_with :llvm do
build 2336
cause 'No thread local storage support'
end
def install
system "make", "-C", "src", "-f", "Makefile.OSX", "PREFIX=#{prefix}"
bin.install 'src/faketime'
(lib/'faketime').install 'src/libfaketime.1.dylib'
man1.install 'man/faketime.1'
end
end

45
packaging/OSX/MacPorts/Portfile
View File

@@ -1,45 +0,0 @@
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
# $Id: Portfile 112093 2013-10-11 19:57:13Z ryandesign@macports.org $
PortSystem 1.0
PortGroup github 1.0
github.setup wolfcw libfaketime 0.9.7 v
checksums rmd160 8874d43bb212976d929c3007db0cf978311b3596 \
sha256 4d65f368b2d53ee2f93a25d5e9541ce27357f2b95e5e5afff210e0805042811e
categories sysutils
platforms darwin
maintainers code-wizards.com:wolf openmaintainer
license GPL-2
description libfaketime modifies the system time for a single application
long_description libfaketime intercepts various system calls that applications use to \
retrieve the current date and time. It can then report user-specified \
faked dates and times to these applications. This allows us to modify \
the system time an application sees without having to change the time \
system-wide. The faketime wrapper can be used from command line. \
Check the documentation on how to integrate into installed applications.
patchfiles patch-test-Makefile.OSX.diff
use_configure no
variant universal {}
compiler.blacklist *cc* *dragonegg*
build.args -f Makefile.OSX
build.env CC="${configure.cc}" \
CFLAGS="[get_canonical_archflags cc]" \
LDFLAGS="[get_canonical_archflags ld]" \
PREFIX=${prefix}
test.run yes
test.args ${build.args}
eval test.env ${build.env}
destroot.args ${build.args}
eval destroot.env ${build.env}

12
packaging/OSX/MacPorts/patch-test-Makefile.OSX.diff
View File

@@ -1,12 +0,0 @@
--- test/Makefile.OSX.orig 2013-10-11 09:42:38.000000000 -0500
+++ test/Makefile.OSX 2013-10-11 14:46:11.000000000 -0500
@@ -1,7 +1,6 @@
-CC = gcc
+CC ?= clang
-CFLAGS = -std=gnu99 -Wall -DFAKE_STAT
-LDFLAGS =
+CFLAGS += -std=gnu99 -Wall -DFAKE_STAT
SRC = timetest.c
OBJ = ${SRC:.c=.o}

65
packaging/OSX/README
View File

@@ -1,65 +0,0 @@
# Packaging for OS X
Several software tools assist with the installation of open source software
on OS X. The authors of libfaketime maintain the libfaketime build spec files
for MacPorts, Homebrew, and Fink.
## MacPorts
Installing libfaketime via MacPorts is based on the provided Portfile, which
has been included in the official MacPorts distribution since October, 2013.
Users therefore can use "sudo port install libfaketime" as installation
command.
Some libfaketime Portfile caveats:
- Github-based source file distribution
- Non-clang-compilers need to be blacklisted
- MacPorts folks have requested to avoid a platform-specific Makefile.OSX in
the future
Portfile submission is documented in https://www.macports.org/guide/#project.contributing
and handled via a ticketing system:
- https://trac.macports.org/ticket/40662
- https://trac.macports.org/ticket/40748
## Homebrew
The libfaketime 'formula' for Homebrew is available since November, 2013.
Homebrew users can use 'brew install libfaketime' as installation command.
Some libfaketime formula caveats:
- "depends_on :macos => :lion" must be set for libfaketime >=0.9.5
- :llvm builds <= 2336 must be blacklisted because libfaketime =0.9.5
requires a compiler with thread local storage support.
Formula submission is handled via pull request on Github following the
"one formula per commit, one commit per formula" rule, which necessitates
squashing commits and forced pushes when applying fixes. Style issues
complementary to the documentation have been discussed in
https://github.com/mxcl/homebrew/pull/23245
## Fink
A libfaketime.info file is included in the Fink 10.7 tree since October,
2013, and installed using
fink install libfaketime
Some libfaketime fink info file caveats:
- The dynamic library must be declared as private Shlib; this also necessitates
BuildDepends: fink (>= 0.28)
- "Distribution: 10.7, 10.8, 10.9" is required because libfaketime >=0.9.5 does
not work on OS X 10.6 or before anymore.
- When compiling, PREFIX=%{p} needs to be used because this path is hardcoded
into the wrapper. However, "make install" needs to deploy into PREFIX=%{i} to
make packaging work.
Submission is via https://sourceforge.net/p/fink/package-submissions/

14
packaging/README
View File

@@ -1,14 +0,0 @@
# libfaketime packaging
Not everyone feels comfortable with installing tools and libraries manually
by downloading and building them from source. Luckily enough, voluntary
maintainers prepare new libfaketime releases for various platforms and make
them available as binary packages or otherwise automatically installable
software.
In this directory, we collect build specification files for the platforms
that we are aware of being actively supported. They help us to analyze
build issues, create awareness for platform-specific patches that had to
be applied and might be merged with our code, and provide the contact
information for future "early release warnings".

5
src/faketime.c
View File

@@ -1,7 +1,7 @@
/*
* libfaketime wrapper command
*
* This file is part of libfaketime, version 0.9.7
* This file is part of libfaketime, version 0.9.8
*
* libfaketime is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License v2 as published by the
@@ -125,7 +125,7 @@ int main (int argc, char **argv)
}
else if (0 == strcmp(argv[curr_opt], "--exclude-monotonic"))
{
setenv("DONT_FAKE_MONOTONIC", "1", true);
setenv("FAKETIME_DONT_FAKE_MONOTONIC", "1", true);
curr_opt++;
continue;
}
@@ -225,6 +225,7 @@ int main (int argc, char **argv)
if (SEM_FAILED == (sem = sem_open(sem_name, O_CREAT|O_EXCL, S_IWUSR|S_IRUSR, 1)))
{
perror("sem_open");
fprintf(stderr, "The faketime wrapper only works on platforms that support the sem_open()\nsystem call. However, you may LD_PRELOAD libfaketime without using this wrapper.\n");
exit(EXIT_FAILURE);
}

686
src/libfaketime.c
View File

File diff suppressed because it is too large Load Diff

13
test/functests/test_exclude_mono.sh
View File

@@ -1,12 +1,12 @@
# Checks that setting DONT_FAKE_MONOTONIC actually prevent
# Checks that setting FAKETIME_DONT_FAKE_MONOTONIC actually prevent
# libfaketime from faking monotonic clocks.
#
# We do this by freezing time at a specific and arbitrary date with faketime,
# and making sure that if we set DONT_FAKE_MONOTONIC to 1, calling
# and making sure that if we set FAKETIME_DONT_FAKE_MONOTONIC to 1, calling
# clock_gettime(CLOCK_MONOTONIC) returns two different values.
#
# We also make sure that if we don't set DONT_FAKE_MONOTONIC to 1, in other
# words when we use the default behavior, two subsequent calls to
# We also make sure that if we don't set FAKETIME_DONT_FAKE_MONOTONIC to 1,
# in other words when we use the default behavior, two subsequent calls to
# clock_gettime(CLOCK_MONOTONIC) do return different values.
init()
@@ -26,7 +26,7 @@ run()
init
run_testcase dont_fake_mono
run_testcase fake_mono
# run_testcase fake_mono
}
get_token()
@@ -64,7 +64,8 @@ get_monotonic_time()
{
dont_fake_mono=$1; shift;
clock_id=$1; shift;
DONT_FAKE_MONOTONIC=${dont_fake_mono} fakecmd "2014-07-21 09:00:00" \
FAKETIME_DONT_FAKE_MONOTONIC=${dont_fake_mono} \
fakecmd "2014-07-21 09:00:00" \
/bin/bash -c "for i in 1 2; do \
perl -w -MTime::HiRes=clock_gettime,${clock_id} -E \
'say clock_gettime(${clock_id})'; \

21
test/functests/test_walkone.sh
View File

@@ -37,7 +37,15 @@ fakedate()
#
typeset fmt='%s'
export FAKETIME_FMT=$fmt
fakecmd "$1" date +$fmt
if [ "mac" == "$PLATFORM" ]; then
if [ -x /usr/local/bin/gdate ] ; then
fakecmd "$1" gdate +$fmt
else
echo "<skip>"
fi
else
fakecmd "$1" date +$fmt
fi
}
#
@@ -63,5 +71,14 @@ test_with_i()
typeset i="$1"
typeset t=$(pow 2 $i)
asserteq $(fakedate $t) $t "(secs since Epoch)"
if [ "mac" == "$PLATFORM" ]; then
if [ -x /usr/local/bin/gdate ] ; then
asserteq $(fakedate $t) $t "(secs since Epoch)"
else
asserteq $t $t "(skipping test, install gdate)"
fi
else
asserteq $(fakedate $t) $t "(secs since Epoch)"
fi
}

46
test/test_OSX.sh
View File

@@ -1,46 +0,0 @@
#!/bin/sh
export DYLD_FORCE_FLAT_NAMESPACE=1
export DYLD_INSERT_LIBRARIES=../src/libfaketime.1.dylib
if [ -f /etc/faketimerc ] ; then
echo "Running the test program with your system-wide default in /etc/faketimerc"
./timetest
echo
else
echo "Running the test program with no faked time specified"
./timetest
echo
fi
echo "Running the test program with absolute date 2003-01-01 10:00:05 specified"
echo "FAKETIME=\"2003-01-01 10:00:05\" ./timetest"
FAKETIME="2003-01-01 10:00:05" ./timetest
echo
echo "Running the test program with START date @2005-03-29 14:14:14 specified"
echo "FAKETIME=\"@2005-03-29 14:14:14\" ./timetest"
FAKETIME="@2005-03-29 14:14:14" ./timetest
echo
echo "Running the test program with 10 days negative offset specified"
echo "FAKETIME=\"-10d\" ./timetest"
FAKETIME="-10d" ./timetest
echo
echo "Running the test program with 10 days negative offset specified, and FAKE_STAT disabled"
echo "FAKETIME=\"-10d\" NO_FAKE_STAT=1 ./timetest"
FAKETIME="-10d" NO_FAKE_STAT=1 ./timetest
echo
echo "Running the test program with 10 days positive offset specified, and sped up 2 times"
echo "FAKETIME=\"+10d x2\" ./timetest"
FAKETIME="+10d x2" NO_FAKE_STAT=1 ./timetest
echo
echo "Running the 'date' command with 15 days negative offset specified"
echo "FAKETIME=\"-15d\" date"
FAKETIME="-15d" date
echo
exit 0

13
test/timetest.c
View File

@@ -26,11 +26,15 @@
#include <sys/time.h>
#include <sys/timeb.h>
#ifndef __APPLE__
#ifdef FAKE_STAT
#include <sys/types.h>
#include <sys/stat.h>
#include <unistd.h>
#endif
#else
#include <unistd.h>
#endif
#ifndef __APPLE__
#include <pthread.h>
@@ -94,7 +98,7 @@ void* pthread_test(void* args)
timeToWait.tv_nsec = now.tv_nsec;
printf("pthread_cond_timedwait: CLOCK_MONOTONIC test\n");
printf("(Intentionally sleeping 1 second...)\n");
printf("(Intentionally sleeping 1 second..., see docs about CLOCK_MONOTONIC test)\n");
fflush(stdout);
pthread_mutex_lock(&fakeMutex);
@@ -127,9 +131,14 @@ int main (int argc, char **argv)
sigset_t mask;
struct sigaction sa;
#endif
#ifndef __APPLE__
#ifdef FAKE_STAT
struct stat buf;
#endif
#endif
/* silence compiler warnings */
printf("%s", 0 == 1 ? argv[0] : "");
#ifndef __APPLE__
pthread_t thread;
@@ -262,9 +271,11 @@ int main (int argc, char **argv)
}
#endif
#ifndef __APPLE__
#ifdef FAKE_STAT
lstat(argv[0], &buf);
printf("stat(): mod. time of file '%s': %s", argv[0], ctime(&buf.st_mtime));
#endif
#endif
return 0;