[genivi-dlt] Patch moving dlt-daemon from FIFO to UDS (was: Issues with mechanism to change log-level)

Tobias Olausson tobias.olausson at pelagicore.com
Wed Oct 5 09:33:14 EDT 2016


Hi,

On 5 October 2016 at 15:22, Jeremiah Foster <jeremiah.foster at pelagicore.com>
wrote:

>
>
> On Wed, Oct 5, 2016 at 4:49 AM, Tobias Olausson <
> tobias.olausson at pelagicore.com> wrote:
>
>> Hi,
>>
>> On 5 October 2016 at 07:17, Lipka, Christoph (ADITJ/SWG) <
>> clipka at jp.adit-jv.com> wrote:
>>
>>> Hi Tobias,
>>>
>>>
>>>
>>> I am interested to try your patch in the mentioned container scenario.
>>> Could you guide me to have a minimal demo setup I can test your patch?
>>> Thanks.
>>>
>>
>> Currently, no. The setup we have is rather large (LXC based containers),
>> but we are working on creating something smaller where we can test this
>> properly. This is a priority issue for us, so we will definitely work on
>> getting it fixed.
>>
>>
>>> Btw: We are currently merging the patch on top of current master to get
>>> a feeling how the daemon might look like and behave. It would be great if
>>> you can also have a look on the patch later.
>>>
>>
>> I would be happy to!
>>
>>
>>>
>>>
>>> @Jeremiah: Might it be possible to handle this as pull request for
>>> community review in github? I anyhow don’t really like the current approach
>>> of sending patches to mailing list, since nearly nobody is checking patches
>>> or gives comments.
>>>
>>
>> I agree, plus it gives much better opportunities to track changes +
>> discussion together.
>>
>
> ​Absolutely. Let's set up a workflow that works for you folks. :-)
>
> For clarity, what do we want to set up? Pull requests for DLT daemon are
> available here: https://github.com/GENIVI/dlt-daemon/pulls I guess Tobias
> will have to clone DLT daemon and create a pull request, no?
>

Yes, that's how I would prefer to work at least (and the rest of my team as
well, I guess)


> If we do that, shouldn't we take the opportunity to create a new branch?
> We tend to always use the 'master' branch in GENIVI and that can cause
> problems sometimes. Perhaps we start a dev branch or similar?
>

> Also, here is the code for the softwarecontainer:
> https://github.com/Pelagicore/softwarecontainer​
>

It's worth mentioning that we're not running using DLT directly but through
a library called ivi-logging (https://github.com/Pelagicore/ivi-logging)
that has DLT as one of its backends.


>
> ​Cheers,
>
> Jeremiah​
>
>
>



-- 
Tobias Olausson
M.Sc C.S.
Software Engineer

PELAGICORE | Experience Change
Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden
Mobile: +46(0)735-873444
http://www.pelagicore.com/
IRC: wto @ FreeNode

Registered Office Gothenburg, Sweden
Registration No. 556780-4199
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-diagnostic-log-and-trace_lists.genivi.org/attachments/20161005/6105e45e/attachment.html>


More information about the genivi-diagnostic-log-and-trace mailing list