> On 07 Nov 2016, at 20:56, Nigel Titley <ni...@homechip.com> wrote:
>
> Yes, that was what we decided was probably the issue, but what we never
> managed to work out was why, having failed to start at bootup, it was
> necessary to stop the service and then start it, even though it wasn't
> running.
This should be a problem within the init system, which is unaware of the fact
that the owserver “failed” to start.
I would classify this problem as downstream, unless there is clear evidence
that owserver fails in an unexpected/undocumented way. I occasionally run
owserver on raspbian, and in my experience “systemctl start/stop/status
owserver” are not 100% reliable. (I suspect that this is linked to the the fact
that in raspbian owserver is started via the old SYSV scripts, and not as a
“type=notify” systemd service. Sorry, but I’ve never had time to investigate.)
S.M.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
