If I use the example program at 
http://blogs.sun.com/praks/entry/file_events_notification
on /proc, it gets errno 48 (ENOTSUP).  This is _not_ helpful (unless there's a 
better
way to be notified of process creation/termination than monitoring /proc for 
changes);
without FEN, it would take a loop that sleeps and stats (or fstat()s) /proc.  
Spinning
like that wastes CPU.

Seen on snv_97, running on a Sun Blade 2000.

(Someone had asked in another thread about whether Linux preload had been ported
to Solaris.  Apparently, it works by monitoring their /proc to discover 
executables and their
libraries, and tries to preload up to a certain amount of some selected by 
means I haven't
examined yet, so that the affected apps will start faster.  I've had a trivial 
preloader of
my own, but it doesn't discover anything, it just operates on a list of 
pathnames it's given.
Trying to make a smarter one that usually just does the right thing probably 
would mean
watching process creation and termination, and I'd prefer if there were an 
efficient way
to do that.)

Even if /proc might never support FEN on all the different objects within /proc
(I can see how that might get complicated and/or have performance issues), 
couldn't
it at least support it on the top-level directory?

And one more strange question: are the timestamps in file_obj argument updated 
when
the event is delivered?  That would make re-associating on the same file more 
efficient
(no need to stat() the file again).
-- 
This message posted from opensolaris.org

Reply via email to