Re: Help with 1-wire/LinkUSB/owfs

["leewild80" <muddyboots@xxxxxxxxx>]

Simon

I'm running both as root, so shouldn't be an issue with allow_other
directi=
ves - but can't hurt to try though.

I'm thinking of setting up a new clean VM just for this, rather than
instal=
l it all directly on my main machine, so maybe these issues might go
away..=
.

Current machine is Fedora 13 (x86_64).
I might setup a simple CentOS 5.5 VM (32 bit), see if it runs on there OK.
I do recall an issue with Fuse though, when I first tried to install owfs
a=
few months ago, that seemed to go away when I updated to the latest fuse r=
ecently - I wonder if this latest update has made it through to CentOS 5.5
=
though. One way to find out I guess !

My biggest problem is time, 2 young kids, full time job, selfbuild to
finis=
h....

Thanks for the help !
Lee

--- In ukha_d@xxxxxxx, Simon Haslam <simon_haslam@...> wrote:
>
> Lee
>=20
> Oh dear - sounds a bit painful. Do you have owserver and owfs running
on =
the same host? (I'd be a bit surprised if iptables was blocking a port on
l=
ocalhost from another process on=A0 the same host)
>=20
> Are you running everything as root (or sudo) to start with? E.g. the
USB =
device needs to be readable by the user running owfs.
>=20
> Note: curiously http://owfs.org/index.php?page=3Dfuse
says that, as well =
as --allow_other in the owfs command line, you should have
user_allow_other=
in /etc/fuse.conf which I don't have, and yet my owfs works OK. Maybe that=
permission is only relevant to the user actually mounting owfs, not access=
ing it (and the allow_other option is redundant in my case as owserver and
=
owfs is run as root from an /etc/init.d script).
>=20
> In my /proc/mounts file here are my 1-wire entries:
> gvfs-fuse-daemon /home/joggler/.gvfs fuse.gvfs-fuse-daemon
rw,nosuid,node=
v,relatime,user_id=3D1000,group_id=3D1000 0 0
> OWFS /var/1w/mnt fuse.OWFS
rw,nosuid,nodev,relatime,user_id=3D0,group_id=
=3D0,allow_other 0 0
>=20
> When I started experimenting with owfs at one point I was running owfs
(d=
irect) and digitemp from crontab which of course caused problems (errors
us=
ually) when they both wanted to use the 1-wire bus at once. I now have all
=
scripts using either OWnet and owfs (both connecting to owserver) and
don't=
have any problems (sometimes an interactive owfs appears to hang for a sec=
ond or two).
>=20
> You could try checking /var/log/messages for errors if you've not done
al=
ready (not quite if the owserver logging goes in there though).
>=20
> I'm still new to this so probably not much help though ;-)=20
>=20
>=20
> Simon
> PS. I found it confusing knowing where you're supposed to put
parameters =
when using both owserver and owfs - I'm assuming you should be putting
1-wi=
re specific ones on owserver (seems most logical to me). I also note you
ha=
ve the device after --link which I also found mentioned in http://owfs.org/=
index.php?page=3Dowserver - again mine looks wrong!
>=20
>=20
>=20=20
>=20
>=20
>=20
>=20=20=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20=20=20=20=20=20=20
>=20
> [Non-text portions of this message have been removed]
>




------------------------------------

<*> Join the Automated Home Forums
http://www.automatedhome.co.uk/vbulletin/