Hi, Daniel Kahn Gillmor: > > libfaketime appears to be capable of intercepting stat() calls while > datefudge is not. > That's been intentional. (One of the uses of datefudge was to test tools like "make", when they run on a file system whose times are skewed.)
> And libfaketime is capable of setting absolute times (i.e. making the > wall clock appear completely stopped for the client). > That's ugly. ;-) > [Datefudge] can't "stop the clock" the way that libfaketime can: > There are a few programs out there which misbehave (i.e. hang) if you do that, so I saw no reason to implement this ... > Both tools seem to be GPL-2 or later, so i see no reason why upstream > couldn't join forces if they wanted to. Wolfgang? Matthias? Do you > guys have any preferences for how to proceed? What do you think of > Guus' suggestion? > If you want to enhance my datefudge code with whatever features libfaketime has that I haven't, be my guest. -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED] Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de - - Howe's Law: Everyone has a scheme that will not work.
signature.asc
Description: Digital signature