Tomasz,
I'm having trouble visualizing how the systemd triggering works. When a
program like owread tries to contact owserver, is owserver started? Is this
done by monitoring the typical owserver port (4304)? How about other
owserver friends?
If you don't mind describing the process more, or givi
On Thu, Jun 05, 2014 at 11:24:47AM -0700, Jerry Scharf wrote:
> Tomasz,
>
> This would need to be an option rather than the default operation mode.
> Not everyone can/will run owserver and friends from systemd.
Systemd's socket activation design makes it very easy to gratefuly
fallback into st
Tomasz,
This would need to be an option rather than the default operation mode.
Not everyone can/will run owserver and friends from systemd.
jerry
On 06/05/2014 07:26 AM, Tomasz Torcz wrote:
> On Tue, Jun 03, 2014 at 10:17:14PM -0400, Paul Alfille wrote:
>> Tomasz, would you use dbus for system
On Tue, Jun 03, 2014 at 10:17:14PM -0400, Paul Alfille wrote:
> Tomasz, would you use dbus for systemd? And would you send 1-wire data that
> way or just program control.
>
> Looking at dbus, it certainly looks like 1-wire data could map to it
> easily. I'm just not sure if it would be useful.
Hi,
I got a LinkUSB as a master for my 1-wire net, around 80m with 30 devices.
The bus is scanned every minute and temperature sensors polled (most of
the devices). Around 3 times a second I try to scan the alarm dir for
alarms (DS2406's), and possibly handle these.
Normally this works perfectly
