Open GoogleCodeExporter opened 9 years ago
Original comment by jonas.fonseca
on 12 Nov 2007 at 10:39
A preliminary patch to show (mainly) which non-code files needs to be changed.
It
doesn't do any advanced filtering on events generated from watched directories,
which
seems to really be the key to get good performance with inotify. Since inotify
only
reports file events 1-level deep, MCH will have to add watches for all
directories
created in /dev/remote. Additionally, adding a watch for one key file such as
the TTY
symlink or the path file will allow very explicit filtering. This will require
that
watch descriptors returned by inotify_add_watch() are stored in a hash to keep
track
of which watch descriptor is a path etc.
Original comment by jonas.fonseca
on 14 Nov 2007 at 8:09
Attachments:
Another benefit from this is that the MCH will be able to run with less
privileges
when the event pipe is not needed, so that only the UDEV scripts requires
administrator permissions.
Original comment by jonas.fonseca
on 14 Nov 2007 at 8:21
Link to good article on inotify: http://www.linuxjournal.com/article/8478
Original comment by jonas.fonseca
on 7 Dec 2007 at 11:17
If this is added after the device hierarchy has been moved to /var/run/remote
it will
greatly simplify the number of inotify watches that will be needed. We will be
able
to only add watches directories:
- /dev/remote to monitor when motes are added
- /dev/remote/MOTEMAC to monitor when the mote TTYs are removed
Original comment by jonas.fonseca
on 22 Mar 2008 at 12:57
Original issue reported on code.google.com by
jonas.fonseca
on 12 Nov 2007 at 9:02