Bug #461

Directories involved in file copies should not check timestamps

Added by Luke Kanies over 5 years ago. Updated 9 months ago.

Status:Accepted Start date:
Priority:Low Due date:
Assignee:- % Done:

0%
Category:fileserving
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:
Votes: 0

Description

When a recursive file copy is being done, there’s no point in checking the directory timestamp, and it can result in extra service restarts.

History

#1
Updated by Benjamin Kite about 5 years ago

  • Status changed from 1 to 2

#2
Updated by Mark Plaksin over 4 years ago

Is this why we get messages like this:

notice: //Node[default]/internal/jables_and_kage/vistaadmin_users/sam/Userfile[sam/.bashprompt]/File[/home/sam/.bashprompt]/checksum: checksum changed ‘{time}Tue Jan 08 18:04:00 -0500 2008’ to ‘{time}Thu Jan 10 18:03:31 -0500 2008’

when nothing has changed?

If so it’s pretty annoying when you’re disributing even a handful of dirs.

#3
Updated by Luke Kanies over 4 years ago

Yes, it is.

#4
Updated by Redmine Admin almost 4 years ago

  • Status changed from 2 to Accepted

#5
Updated by Nigel Kersten over 1 year ago

  • Assignee deleted (Benjamin Kite)
  • Priority changed from Normal to Low

#6
Updated by James Turnbull 9 months ago

  • Target version deleted (4)

Also available in: Atom PDF