Puppet: System Administration Automated

Support

Ticket #461 (assigned defect)

Opened 2 years ago

Last modified 7 months ago

Directories involved in file copies should not check timestamps

Reported by: luke Assigned to: ajax (accepted)
Priority: normal Milestone: unplanned
Component: fileserving Version: 0.22.0
Severity: normal Keywords:
Cc: Triage Stage: Accepted
Attached Patches: None Complexity: Easy

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.

Change History

01/30/07 19:00:19 changed by luke

  • milestone set to grover.

04/05/07 22:38:33 changed by luke

  • specification set to Unnecessary.
  • patch set to None.
  • complexity set to Easy.
  • milestone changed from grover to unplanned.
  • approval set to Unnecessary.
  • compatibility set to Limited.
  • stage set to Accepted.

05/09/07 21:43:06 changed by ajax

  • owner changed from luke to ajax.
  • status changed from new to assigned.

02/15/08 15:01:55 changed by happymcplaksin

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.

02/15/08 16:39:01 changed by luke

Yes, it is.

04/24/08 06:50:37 changed by luke

  • component changed from library to fileserving.