BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Sync Revisited: inotify
- Subject: [Discuss] Sync Revisited: inotify
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Wed, 30 Jul 2014 20:32:48 -0400
- In-reply-to: <53D96A57.6090604@gmail.com>
- References: <53D82930.9050703@gmail.com> <CAOTD2YTGZ83L0LiGP55OxxLtX2HZUm_us2YPA504_wYw8XpjiQ@mail.gmail.com> <53D900E0.4070107@gmail.com> <CAPiok-rj4ju5K6exgkRfe3wwLrShFq19fMhcGvOJkrZGN6vk9g@mail.gmail.com> <53D92110.90102@gmail.com> <53D96A57.6090604@gmail.com>
On 7/30/2014 5:57 PM, Tom Metro wrote: > This could be avoided with architectural changes. Specifically using > inotify[1] on Linux to monitor a file system. (See also fsnotify[2].) A This fails to account for changes made while the tool is not running. If you want to detect such changes then the entire directory tree must be scanned and the results compared with the sync database when the tool starts. The file system can be actively monitored for changes once the tool is running. -- Rich P.
- References:
- [Discuss] Sync Revisited
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Sync Revisited
- From: matt at mattshields.org (Matt Shields)
- [Discuss] Sync Revisited
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Sync Revisited
- From: johnhall2.0 at gmail.com (John Hall)
- [Discuss] Sync Revisited
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Sync Revisited: inotify
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] Sync Revisited
- Prev by Date: [Discuss] Sync Revisited: inotify
- Next by Date: [Discuss] Looking for WiFi router with certain characteristics
- Previous by thread: [Discuss] Sync Revisited: inotify
- Next by thread: [Discuss] Sync Revisited
- Index(es):
