The server will only overwrite the mac if it is zero.
Ths allows acting in place of (non-alfred) legacy clients
by injecting their data with the correct source mac.
Signed-off-by: Dominik Heidler
---
unix_sock.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a
Am 17.02.2016 um 09:39 schrieb Sven Eckelmann:
> Your patch also doesn't explain why this feature may be required.
I'm running an alfred master server with this patch, so that I can run a script
that will
inject data of legacy clients (that don't have an alfred slave, but need to be
crawled).
R
The server will only overwrite the mac if it is zero.
Signed-off-by: Dominik Heidler
---
The alfred client sets the mac to zero by default
so this shouldn't break existing behaviour.
unix_sock.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/unix_sock.c b/unix_s
Is the hook executed as well when the data is pushed from another master node?
Regards,
Dominik
Am 4. Oktober 2015 18:27:54 MESZ, schrieb Sven Eckelmann :
>On Sunday 04 October 2015 18:22:54 Dominik Heidler wrote:
>> ah so the update hook is only executed, when the master gets the dat
Hi,
ah so the update hook is only executed, when the master gets the data update
via UDP.
In my testsetup I updated the master data directly via Unix socket on the
master.
Regards,
Dominik
Am 4. Oktober 2015 18:17:56 MESZ, schrieb Sven Eckelmann :
>On Sunday 04 October 2015 16:23:28 Domi
gt;data.header.type);
177
178 hash_remove_bucket(globals->data_hash, hashit);
179 free(dataset->buf);
180 free(dataset);
181 }
Is this the way the update-command should work or am I doing something
wrong?
Regards,
Dominik Heidler
