Ok, glad to hear multiple processes is not a problem. Thank you so much for the quick response.
You were right, the OWW (one wire weather) 'owwnogui' process was causing the problem in being
able to read from http://192.168.1.77:3001/ consistently.
That is no longer a problem.
ANYONE READING: DO not run OWW(one wire weather) along with OWFS at the same time.
Under the virtual file system /tmp/1wire/*
I have what seems like an endless file system
As well as other directories in/under uncached such as:
alarm, interface, settings, simultaneous, statistics, structure, system
Is this normal?
----- Original Message ----
From: Paul Alfille <paul.alfille@...>
Sent: Thursday, April 3, 2008 8:22:14 PM
Subject: Re: [Owfs-developers] NSLU2: owhttpd Webserver not reachable with browser
That's right. The multiple listing is not a bug. Multithreaded programs are listed for each thread.
I notice that you are running oww and owfs. They will probably compete for the actual 1-wire adapter. oww is particular will poll the 1-wire bus periodically.
At some point a shim oww to access the 1-wire bus via owfs is planned, but it's a slow process.
I'm not sure why you can see the 1-wire bus with owfs but not owhttpd. One problem might be that owhttpd isn't on port 3001. I can't tell which port from the command lines shown. If no owhttpd port is specified, an ephemeral port is assigned by the OS, usually relatively random and hard to locate. Can you show the startup script or configuration file?
On Thu, Apr 3, 2008 at 5:41 PM, Alessio Sangalli <alesan@...> wrote:
> I have the same problem!!!! PLEASE HELP!
> shows multiple processes running for OWFS, OWFTPD, OWSERVER, OWHTTPD
> Has anyone found a solution, or why this is happening???
Maybe you have activated threads support in OWFS? Beware, I'm a very
novice in OWFS I might very well be wrong.
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
Owfs-developers mailing list