On Sun, Apr 25, 2010 at 3:39 AM, Steinar Midtskogen
<stei...@latinitas.org> wrote:
> I did some more testing.  It turns out that the version doesn't
> matter.  It's just that sometimes I get an empty bus, sometimes not.
> A restart of owserver seems to be what it takes to change it.
> Digitemp, however, always lists everything.
>
> The setup: Linux PC->owserver->5 m active USB extension
> cord->USB-RS232 converter (pl2303)->DS9097U->UVI sensor.

Interesting. Perhaps turning on debugging would give some hints of
where the problem lies.
My money is on the pl2303 driver that I've had trouble with.

>
> This is just a test setup.  When I get the sensor properly installed,
> everything might be ok in that setup.

I hope so. I did my test with the DS9490 USB bus master in the last message.
I just tried the DS9097U (directly connected to a serial port) and that works.
And finally the DS9097U with a pl2303 and it works.
Again this isn't with lengthy cables.

>
> I've previously seen owserver miss devices that digitemp reports, but
> that has involved 1-wire hub(s).  An owserver restart seems to fix it
> in those cases as well, at least for a few hours until devices begin
> to disappear again.  I wonder if this is the same thing.

I don't know. The newest version 2.7p36 reworks some of the owserver
handling and might be better. I'd appreciate if you could give it a test.

>
> By the way, an idea for owserver (perhaps as an option): let it fork
> at startup, let the child do the usual stuff and have the parent
> restart if the child crashes.  In my pretty complex setups, owserver
> crashes happen from time to time (usually days or weeks apart for
> 2.7p22, later versions seem more unstable), so I use an external
> watchdog to restart owserver when it dies.  I haven't been able to
> figure out what causes these crashes or disappearing devices.  I've
> had one setup with about 20 devices that never has had any problems,
> currently owserver was started 323 days ago, still running...
>

In my longest running implementation, I start owserver from inittab, which
does exactly what you describe. (Restart on crash).

Do you have any example code for this? Forking is no problem, we already fork
for entering background. I'm a little wary of signal handling, and how well this
will work on all platforms (uClibc for instance).

Paul Alfille

------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to