Slava> Try running the io.monitors tests to see if inotify is working on
Slava> your system:
The test run ends as follows --- it's not clear to me whether this is a
pass or not, but I get this same result on another system on which
refresh works correctly:
Unit Test: {
[ ]
[
mock-io-backend io-backend [
"" resource-path <mailbox> <recursive-monitor>
[ dispose ] [ dispose ] bi
] with-variable
]
}
Error in thread 52 (Recursive monitor pump, [ ~recursive-monitor~ pump-thread
]):
Unix system call âlstatâ failed:
No such file or directory (2)
It was called with the following arguments:
"/home/conrad/factor/factor-clean-linux-x86-32/temp/doesnotexist"
S{ stat f 0 0 0 0 0 0 0 0 ~ushort-array~ 0 0 0 ~timespec~...
[ call -> stop ]
pump-thread
add-child-monitor
M\ unix link-info
link-status
unix-system-call-error
M\ object throw
[
63 getenv error-thread set-global
continuation -> error-continuation set-global rethrow
]
( scratchpad )
This is in basis/io/monitors/recursive/recursive-tests.factor;
monitors-tests and linux-tests appear to have completed.
Slava> is /tmp some kind of special in-memory file system or something?
It is, but I get the same results on a local ext3 file system mounted off
/dev/hda1.
Thanks for the clarification re: vocabulary roots.
Conrad
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
