You summarized the problem well. Synchronizing the start of owserver and
it's clients can be problematic.

As for suspending the boot process -- the whole scheme can be done in the
background.

I.e run this script in the background:

#!/bin/sh
# script to start the 1-wire processes
# with delay for owserver

# owserver address
address=""
/opt/owfs/bin/owserver --fake=10 -p $address

# wait for owserver to accept connections:
e="1"
while [ $e -ne 0 ] ; do
  /opt/owfs/bin/owexist -q $address
  e=$?
  sleep 1
done

/opt/owfs/bin/owhttpd -s $address -p 4444
/opt/owfs/bin/owfs      -s $address -m /mnt/1wire --allow_other

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

I guess another approach would be to allow owhttpd and owfs to function
even if they can't yet connect to owserver.


On Mon, May 21, 2012 at 3:37 PM, Eloy Paris <pe...@chapus.net> wrote:

> I know that in my case owserver takes a while to start. It sounds like
> the same problem as "late-starting owservers" but I cannot seem to find
> the February 1st report that Klas mentions.
>
> Based on Paul's comment below, I take it that the problem has been
> identified and will be fixed in the next release?
>
> This has been a problem for me because my owfs start script cannot
> execute owserver and owfs in succession because owserver goes daemon
> immediately but does not really start servicing requests, and then owfs
> fails to find a working owserver and then quits. So, after each reboot I
> need to run owfs manually. Fortunately I don't restart my server often.
>
> I'll look into that owexist trick that Paul mentions, though it does not
> seem to be perfect because it would suspend the boot process for a
> little bit.
>
> Cheers,
>
> Eloy Paris.-
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to