Using this structure makes diffs easier to read, when changes are due.
The underlying formatting produced by groff ends up basically the same
(though some versions of groff may adjust to have two spaces after a
sentence-ending period instead of one).
I had to decide what to do if FAKE_PID wasn't defined during the
build. I decided that since the wrapper can't be sure it is preloading
the same library that it was built with (someone could somehow mix and
match the library and the wrapper tool), it should just warn and pass
along the value anyway.
This reserves the option space, but shouldn't annoy people too much if
they are running it on a system that doesn't have FAKE_PID enabled.
I note that this happens regardless of whether it is a "direct"
invocation or not. I don't fully understand all the tradeoffs here,
so I would appreciate another set of eyes reviewing this choice.
Closes: #308
It's hard to notice the tiny reference to `fstat(2)` amongst all the text about the system clock. This is a significant behaviour that is very surprising, and the default setting (on) messes with buildsystems in a counter-intuitive way. Also document how to switch it off.
In case the clock is set to advance with each faked time(), etc. call, the
counter uses the same clock counter stored in shared memory and protected
by a semaphore.
Used (emacs) M-x untabify for whole faketime.c as the prevailing
style in that file used spaces for indentation.
Used M-x delete-trailing-whitespace to all files that had either
trailing whitespace or empty lines at the end of file to remove
those.
Add "-f" option to gzip(1) invocation to avoid user prompts if
compressed man pages already exist in the target directory.
Signed-off-by: Lukas Fleischer <info@cryptocrack.de>
* Create separate "install" and "uninstall" targets for man pages.
* Add man page targets to the shortcut Makefile.
Signed-off-by: Lukas Fleischer <info@cryptocrack.de>
