Fixed bug caused by missing set of paranthesis when checking the modification
time. This caused differences in the nanosecond portion of the time to screwup the logic and made mtree think it should compare the modtime even though "time" wasn't specified. The end result is that mtree couldn't deal with procfs because procfs sets the mtime with high accuracy via microtime().
This commit is contained in:
parent
8380e16daa
commit
de85bb46bf
@ -169,9 +169,9 @@ typeerr: LABEL;
|
|||||||
* XXX
|
* XXX
|
||||||
* Catches nano-second differences, but doesn't display them.
|
* Catches nano-second differences, but doesn't display them.
|
||||||
*/
|
*/
|
||||||
if ((s->flags & F_TIME &&
|
if ((s->flags & F_TIME) &&
|
||||||
s->st_mtimespec.ts_sec != p->fts_statp->st_mtimespec.ts_sec) ||
|
((s->st_mtimespec.ts_sec != p->fts_statp->st_mtimespec.ts_sec) ||
|
||||||
(s->st_mtimespec.ts_nsec != p->fts_statp->st_mtimespec.ts_nsec)) {
|
(s->st_mtimespec.ts_nsec != p->fts_statp->st_mtimespec.ts_nsec))) {
|
||||||
LABEL;
|
LABEL;
|
||||||
(void)printf("%smodification time (%.24s, ",
|
(void)printf("%smodification time (%.24s, ",
|
||||||
tab, ctime(&s->st_mtimespec.ts_sec));
|
tab, ctime(&s->st_mtimespec.ts_sec));
|
||||||
|
Loading…
Reference in New Issue
Block a user