On Wed, 29 Jun 2011 20:57:47 -0700 "Enlightenment SVN" <no-re...@enlightenment.org> wrote:
> Log: > make eeze_scanner suid > > Author: discomfitor > Date: 2011-06-29 20:57:47 -0700 (Wed, 29 Jun 2011) > New Revision: 60856 > Trac: http://trac.enlightenment.org/e/changeset/60856 > > Modified: > trunk/eeze/src/bin/Makefile.am > okay, here's how the scanner works in conjunction with EFM. using a step-by-step process: 0) start e, which starts EFM and scanner 1) scanner reads hw storage devices 2) scanner starts write-only server on local socket (scanner never reads from socket) 2a) EFM connects to socket 3) scanner writes serialized (using eet_connection over ecore-con) device events to socket 3a) device events are picked up by EFM 4) EFM uses enlightenment_sys to actually perform the mount/umount/eject operation. to ensure the user has permissions, sysactions.conf must be properly set up to include the actual /path/to/{mount,umount,eject} binaries. 5) EFM crashes due to bugs 5a) blame cedric 5b) goto 0 -- Mike Blumenkrantz Zentific: Coding in binary since '10. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
