Pascal Baerten <pascal.baerten <at> gmail.com> writes: > > > Hi Eduard,As said earlier, my slug is under debian so I cannot tell about unslung. As I cannot reproduce the problem my self, you have to capture some debug output from owfs to get a chance to get the problem solved.Here my method to capture debug messages:start your owfs daemon with adding command-line parameters: --foreground --errorlevel 8 and ensure that you have large enough scrollback buffer in your terminal. > Then from another session access to the offending properties and send back to the list both the action details along with the trace in a tar.gz file.Of course this log is quite verbose and you should try to limit to the minimum the actions needed that illustrate the behaviour. > a command as simple as below could already produce some interesting trace: (of course adapt with your path) > > echo 1 > /tmp/ow/bus.0/29.9B0204000000/PIO.0 > > Again to avoid large output generated when traversing the directories, prepare this command then restart a fresh owfs instance.Pascal2010/2/9 Eduard <draude <at> gmail.com>
Pascal, I don't know how to post the log file but using the following link you can access the log file. http://efreeman.demon.nl/unslung/owfs.txt I executed two commands, one to change PIO.0 and one to change PIO.BYTE. PIO.0 isn't working. PIO.BYTE is working. Both are mentioned inside the log file. ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
