e it easier if I somehow use
sd_bus_message_append() to assemble the message. But I don't see a clear
path either.
Also, the length of the array can be one or two. So that bit is variable
too.
Thanks for any hints
Tilman Baumann
___
systemd-devel mail
Any hint?
I would be happy to just see some similar code that deals with arrays of
complex structures. If I see a example that is similar, I'm sure I can
learn from it.
So if anybody knows of a code example that does that...
Thanks
On 19.07.2017 11:20, Tilman Baumann wrote:
> Hi folks,
>
On 21.07.2017 14:35, Lennart Poettering wrote:
> On Wed, 19.07.17 11:20, Tilman Baumann (til...@baumann.name) wrote:
>
>> My guess is that I can have it easier if I somehow use
>> sd_bus_message_append() to assemble the message. But I don't see a clear
>> path eit
of those nasty ppp over ssl jobs. And the only
fields passed down to the client are the nameservers.
Cheers
Tilman
On 21.07.2017 14:35, Lennart Poettering wrote:
> On Wed, 19.07.17 11:20, Tilman Baumann (til...@baumann.name) wrote:
>
>> Hi folks,
>>
>> I'm trying
On 21.07.2017 14:44, Tilman Baumann wrote:
> On 21.07.2017 14:35, Lennart Poettering wrote:
>> On Wed, 19.07.17 11:20, Tilman Baumann (til...@baumann.name) wrote:
>>
> >> My guess is that I can have it easier if I somehow use
>>> sd_bus_message_append() to asse
On 09.08.2017 11:28, Tilman Baumann wrote:
> DL;DR
> UPS shutdowns are tricky. Clean file-systems are not the only concern.
> But if you can make assumptions about your storage backend you might be
> able to cut corners safely.
>
> In my experience, the only place where you can
DL;DR
UPS shutdowns are tricky. Clean file-systems are not the only concern.
But if you can make assumptions about your storage backend you might be
able to cut corners safely.
In my experience, the only place where you can hook in a non racy way is
in the kernel.
