Paul Lathrop writes: > When a file in the directory changes, it will change the mtime of the > directory which will trigger an event on any resources which subscribe > to the directory. > > I have used this method a number of times to great success.
The mtime on the directory won't change unless some kind of manipulation of the directory itself occurs in the process of changing a file within the directory. This happens with a lot of editors that create temporary or backup files in the same directory as the file being edited, but isn't absolutely assured. For example: drwxr-xr-x 3 root root 4096 Oct 27 17:39 . drwxr-xr-x 5 root root 4096 Aug 17 2007 .. -rw-r--r-- 1 root root 75576 Nov 7 11:54 access In particular this is actually what a directory in our Puppet subversion repository looks like; as no new files have been added or removed in the repository since October 27, subversion hasn't had to manipulate the directory itself, so the directory mtime hasn't changed even though many files have been updated frequently since. If Puppet's "mtime" tracking looks only at the mtime of the directory and not at the mtime of anything underneath it, you wouldn't be able to depend on that to track changes to files within the directory, unless you also happen to do something to the directory every time you change a file underneath it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
