summaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorTomi Ollila <too@iki.fi>2012-08-26 22:34:39 +0300
committerTomi Ollila <too@iki.fi>2012-08-30 10:46:58 +0300
commitb648b7712d02670089228a22544708abe5b048b1 (patch)
tree446cad86aa6fa7116392aa556ebed5d5ea5b4378 /man
parentd8053c280c0091f51df8715607b8e2535940790b (diff)
downloadlibfaketime-b648b7712d02670089228a22544708abe5b048b1.tar.gz
whitespace cleanup
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.
Diffstat (limited to 'man')
-rw-r--r--man/faketime.114
1 files changed, 7 insertions, 7 deletions
diff --git a/man/faketime.1 b/man/faketime.1
index 6e0cdaa..cc6d52c 100644
--- a/man/faketime.1
+++ b/man/faketime.1
@@ -8,10 +8,10 @@ faketime \- manipulate the system time for a given command
.\" \fIfaketime\fR will trick the given program into seeing the specified timestamp as its starting date and time.
.PP
The given command will be tricked into believing that the current system time is the one specified in the timestamp. The wall clock will continue to run
-from this date and time unless specified otherwise (see advanced options). Actually, faketime is a simple wrapper for libfaketime, which uses the LD_PRELOAD
+from this date and time unless specified otherwise (see advanced options). Actually, faketime is a simple wrapper for libfaketime, which uses the LD_PRELOAD
mechanism to load a small library which intercepts system calls to functions such as
\fItime(2)\fR and \fIfstat(2)\fR. This wrapper exposes only a subset of libfaketime's functionality; please refer to the README file that came with faketime
-for more details and advanced options.
+for more details and advanced options.
.SH OPTIONS
.TP
\fB\-\-help\fR
@@ -44,21 +44,21 @@ Freeze clock at absolute timestamp: \fB"YYYY-MM-DD hh:mm:ss"\fR
If you want to specify an absolute point in time, exactly this format must be used. Please note that freezing the clock is usually not what you want and may break the application. Only use if you know what you're doing!
.TP
Relative time offset: \fB"[+/-]123[m/h/d/y]\fR, e.g. "+60m", "+2y"
-This is the most often used format and specifies the faked time relatively to the current real time. The first character of the format string \fBmust\fR be a + or a -. The numeric value by default represents seconds, but the modifiers m, h, d, and y can be used to specify minutes, hours, days, or years, respectively. For example, "-2y" means "two years ago". Fractional time offsets can be used, e.g. "+2,5y", which means "two and a half years in the future". Please note that the fraction delimiter depends on your locale settings, so if "+2,5y" does not work, you might want to try "+2.5y".
+This is the most often used format and specifies the faked time relatively to the current real time. The first character of the format string \fBmust\fR be a + or a -. The numeric value by default represents seconds, but the modifiers m, h, d, and y can be used to specify minutes, hours, days, or years, respectively. For example, "-2y" means "two years ago". Fractional time offsets can be used, e.g. "+2,5y", which means "two and a half years in the future". Please note that the fraction delimiter depends on your locale settings, so if "+2,5y" does not work, you might want to try "+2.5y".
.TP
Start-at timestamps: \fB"@YYYY-MM-DD hh:mm:ss"\fR
-The wall clock will start counting at the given timestamp for the program. This can be used for specifying absolute timestamps without freezing the clock.
+The wall clock will start counting at the given timestamp for the program. This can be used for specifying absolute timestamps without freezing the clock.
.SH ADVANCED USAGE
When using relative time offsets or start-at timestamps (see ADVANCED TIMESTAMP FORMAT above and option \fB\-f\fR), the clock speed can be adjusted, i.e. time may run faster or slower for the executed program. For example, \fB"+5y x10"\fR will set the faked time 5 years into the future and make the time pass 10 times as fast (one real second equals 10 seconds measured by the program). Similarly, the flow of time can be slowed, e.g. using \fB"-7d x0,2"\fR, which will set the faked time 7 days in the past and set the clock speed to 20 percent, i.e. it takes five real world seconds for one second measured by the program. Again, depending on your locale, either "x2.0" or "x2,0" may be required regarding the delimiter.
.PP
Faking times for multiple programs or even system-wide can be simplified by using ~/.faketimerc files and /etc/faketimerc. Please refer to the README that came with faketime for warnings and details.
.SH AUTHOR
-Maintained by Wolfgang Hommel <wolf@code-wizards.com>. Please see the README and Changelog files for contributers.
+Maintained by Wolfgang Hommel <wolf@code-wizards.com>. Please see the README and Changelog files for contributers.
.SH BUGS
-Due to limitations of the LD_PRELOAD mechanism, faketime will not work with suidroot and statically linked programs.
+Due to limitations of the LD_PRELOAD mechanism, faketime will not work with suidroot and statically linked programs.
While timestamps and time offsets will work for child processes, speeding the clock up or slowing it down might not
work for child processes spawned by the executed program as expected; a new instance of libfaketime is used for each
-child process, which means that the libfaketime start time, which is used in speed adjustments, will also be
+child process, which means that the libfaketime start time, which is used in speed adjustments, will also be
re-initialized.
.SH "REPORTING BUGS"
Please send an e-mail to Wolfgang Hommel <wolf@code-wizards.com>