Add freebsd rc script #15
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
And re-organize the sources accordingly. There is no reason to make this LIFX specific. --HG-- rename : core/lifxd.c => core/lightsd.c rename : core/lifxd.h => core/lightsd.h rename : core/broadcast.c => lifx/broadcast.c rename : core/broadcast.h => lifx/broadcast.h rename : core/bulb.c => lifx/bulb.c rename : core/bulb.h => lifx/bulb.h rename : core/gateway.c => lifx/gateway.c rename : core/gateway.h => lifx/gateway.h rename : core/timer.c => lifx/timer.c rename : core/timer.h => lifx/timer.h rename : core/wire_proto.c => lifx/wire_proto.c rename : core/wire_proto.h => lifx/wire_proto.h
This avoid stupid infinite loops on ENETUNREACH for example.
Use the j modifier when printing 64bits numbers.
Just call the callback for the discovery timeout event right away, it starts the discovery and setup everything already...
A quick look around showed me that this project can perfectly run on iOS and Android and it changed my perspectives.
…eway lgtd_gateway_handle_light_status is called per bulb and not per gateway and we trigger the refresh of all the bulbs on the gateway from this function. This means that we could potentially enqueue multiple GET_LIGHT_STATE packets for all bulbs on the same gateway within a single libevent iteration. With this changeset each gateway now keep track of when the last GET_LIGHT_STATE for all bulbs was sent. If it's more recent than when the last packet was sent then we know that one has already been enqueued.
Huuu we do need this file on linux, and I do need to step continuous testing.
Fix build warnings on apple/clang.
Readings of lifx-gem & LIFXKit revealed the actual purpose of this field.
We actually need that to support tagging.
We'll need this for debugging soon enough and to return real responses as well.
By using intmax_t and %jd in lgtd_isotime_now.
This is will be needed to support tagging.
This should significantly improve both latency and throughput.
This finishes what started the previous changeset: mock the wire_proto module and properly do unit testing.
- properly set res required; - properly listen on each gateway's socket; - improved traffic logging.
Thanks a lot to /u/nullcompany for his feedback about the protocol documentation: https://www.reddit.com/r/lifx/comments/3s82yy/restrict_from_the_cloud/cxfnxlf
It now handles arbitrarily large and partial responses properly.
After all people who don't use apt-get will figure it out...
|
like I say its not a major problem, and as it stays in the forground you On 10 May 2016 at 07:35, Louis Opter notifications@github.com wrote:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: i am not using the daemon flag as this doesnt appear to work, and the process just exits without forking to the background. So for the time being im running it in the foreground and utilizing the base system daemon command.