On Dec 6, 2007 7:24 PM, Decibels <[EMAIL PROTECTED]> wrote:
> I am still not understanding a couple things. Best way to start the Owfs
> and
> what about stopping it?
If you mean owserver, you can start it from the command line, from a system
service, from inittab, or perhaps even from a udev script whenever the
adapter is detected.
Same for owhttpd.
owfs the filesystem can be started the same way, of in fstab like all the
other filesystems. modfuse has to be loaded, however.
>
> I did a 'killall owserver' is that the best way.
>
Sure. There is no "in band" way of stopping owserver (no tcp message).
Having a client able to kill a server doesn't seem like good design in
general, especially in a relatively open architecture like owserver.
>
> And is there a preference for setup like mine with the computer/interface
> hub connected and doing the reading to starting it? ie.
> I started this way on the amd64 system, but can't seem to on the x86 box.
> I
> have to start owfs there.
>
> AMD64 (don't remember starting owfs it was like the owserver started it.)
> 1) This way isn't working on the x86 box. I am sure copied what did on
> amd64
> correct.
> owserver -d /dev/ttyS0 -p 3000
fine as long as the user has access permission to the serial port.
>
> ROOT # owdir localhost:3000 ~/1wire
Not correct syntax for owdir. either: "owfs -s localhost:3000 -m ~/1wire" or
"owdir -s localhost:3000 /"
In other works, ~/1wire isn't a valid owfs path, just a mountpoint.
>
> Paul Alfille
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
