Thanks Christian Sorry for the delay, cvs doesn't happen from work, so had to wait.
It didnt work though, owserver stays resident, but the second owdir doesn't show any devices. I'll snag the syslog and post it later. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Magnusson Sent: Friday, 24 November 2006 7:24 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Problems Hi again Matt, I have made some more change/cleanup in both the signal-handling and threads in ow_net now. Check out the latest cvs in a few minutes or hours when the anonymous cvs is updated. The SIGHUP signal you got was generated by the kernel! (no user application and general exception from libc). I'm not sure why, but could it be something like selinux which cause this? Can you test something like this... and then look at the error-counters (if owserver still works) owserver -d /dev/ttyS0 --error_level=9 -p 3000 owdir -p 3000 /uncached/ (does owserver still die?) owdir -p 3000 /uncached/ owfs -s 3000 /tmp/1wire grep -v " 0" /tmp/1wire/bus.0/statistics/errors/* /Christian On Mon, 2006-11-20 at 13:59 +0100, Christian Magnusson wrote: > Your system obviously send a SIGHUP to your owserver process for some > reason? It's catched in the main-process and ignores it right now. > > > Nov 16 12:32:53 localhost OWFS[19068]: Signal handler for 1, errno 0, code > > 128, pid 0 > > The strange thing is that info->si_pid = 0... I'm not sure why it's like > this, but I'll make some more experiments and see if I can block the SIGHUP > signal in some other ways. It might still be some thread which doesn't > handle SIGHUP and dies at that point. > > FS_read_postpostparse/FS_r_given_bus seem to return -22 (EINVAL) during the > failed read, and Paul might have some idea when this occurs. > > /Christian > > > > -----Ursprungligt meddelande----- > > Från: [EMAIL PROTECTED] [mailto:owfs- > > [EMAIL PROTECTED] För Matt > > Skickat: den 20 november 2006 12:06 > > Till: owfs-developers@lists.sourceforge.net > > Ämne: Re: [Owfs-developers] Problems > > > > Sorry, I thought I had posted my results. > > No, the latest owserver didn't work, I get one result, then no results. > > The owserver process keep running, doesn't quit like with the previous > > build. (<13102006). > > > > Below is the results for a successful read, then a failed read. > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
