xz.git - XZ Utils

Age	Commit message (Collapse)	Author	Files	Lines
2023-02-07	xz: Improve the comment about start_time in mytime.c.	Lasse Collin	1	-5/+10
	start_time is relative to an arbitary point in time, it's not time of day, so using it for anything else than time differences wouldn't make sense.
2023-02-04	xz: Add a comment clarifying the use of start_time in mytime.c.	Jia Tan	1	-0/+5

2023-01-27	xz: Use clock_gettime() even if CLOCK_MONOTONIC isn't available.	Lasse Collin	1	-3/+8
	mythread.h and thus liblzma already does it.
2023-01-27	xz: Add SIGTSTP handler for progress indicator time keeping.	Lasse Collin	1	-1/+55
	This way, if xz is stopped the elapsed time and estimated time remaining won't get confused by the amount of time spent in the stopped state. This raises SIGSTOP. It's not clear to me if this is the correct way. POSIX and glibc docs say that SIGTSTP shouldn't stop the process if it is orphaned but this commit doesn't attempt to handle that. Search for SIGTSTP in section 2.4.3: https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html
2022-12-30	xz: Includes <time.h> and <sys/time.h> conditionally in mytime.c.	Jia Tan	1	-1/+3
	Previously, mytime.c depended on mythread.h for <time.h> to be included.
2022-12-30	Build: No longer require HAVE_DECL_CLOCK_MONOTONIC to always be set.	Jia Tan	1	-3/+2
	Previously, if threading was enabled HAVE_DECL_CLOCK_MONOTONIC would always be set to 0 or 1. However, this macro was needed in xz so if xz was not built with threading and HAVE_DECL_CLOCK_MONOTONIC was not defined but HAVE_CLOCK_GETTIME was, it caused a warning during build. Now, HAVE_DECL_CLOCK_MONOTONIC has been renamed to HAVE_CLOCK_MONOTONIC and will only be set if it is 1.
2020-01-26	xz: Set the --flush-timeout deadline when the first input byte arrives.	Lasse Collin	1	-1/+0
	xz --flush-timeout=2000, old version: 1. xz is started. The next flush will happen after two seconds. 2. No input for one second. 3. A burst of a few kilobytes of input. 4. No input for one second. 5. Two seconds have passed and flushing starts. The first second counted towards the flush-timeout even though there was no pending data. This can cause flushing to occur more often than needed. xz --flush-timeout=2000, after this commit: 1. xz is started. 2. No input for one second. 3. A burst of a few kilobytes of input. The next flush will happen after two seconds counted from the time when the first bytes of the burst were read. 4. No input for one second. 5. No input for another second. 6. Two seconds have passed and flushing starts.
2020-01-26	xz: Move flush_needed from mytime.h to file_pair struct in file_io.h.	Lasse Collin	1	-3/+0

2019-06-23	xz: Fix some of the warnings from -Wsign-conversion.	Lasse Collin	1	-2/+2

2013-07-04	xz: Move some of the timing code into mytime.[hc].	Lasse Collin	1	-0/+89
	This switches units from microseconds to milliseconds. New clock_gettime(CLOCK_MONOTONIC) will be used if available. There is still a fallback to gettimeofday().