From 69f9ff7d82484803d589e6570e8989b49f3dde2c Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Sun, 14 Sep 2014 17:52:07 +0200 Subject: unix_msg: remove cookie from unix_msg_init "pid" and "sock" are sufficient I guess as randomizers to distinguish messages. In theory, a pid could be recycled very quickly, which might mix up in-flight messages. But once a few messages have passed, "cookie" would be incremented as another indicator of a fresh message. Why? Remove messages_dgm dependency on samba-util Signed-off-by: Volker Lendecke Reviewed-by: Stefan Metzmacher --- source3/lib/unix_msg/tests.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) (limited to 'source3/lib/unix_msg/tests.c') diff --git a/source3/lib/unix_msg/tests.c b/source3/lib/unix_msg/tests.c index df094afb3d..9a15f9dff1 100644 --- a/source3/lib/unix_msg/tests.c +++ b/source3/lib/unix_msg/tests.c @@ -70,16 +70,14 @@ int main(void) return 1; } - ret = unix_msg_init(&addr1, funcs, 256, 1, - recv_cb, &state, &ctx1); + ret = unix_msg_init(&addr1, funcs, 256, recv_cb, &state, &ctx1); if (ret != 0) { fprintf(stderr, "unix_msg_init failed: %s\n", strerror(ret)); return 1; } - ret = unix_msg_init(&addr1, funcs, 256, 1, - recv_cb, &state, &ctx1); + ret = unix_msg_init(&addr1, funcs, 256, recv_cb, &state, &ctx1); if (ret == 0) { fprintf(stderr, "unix_msg_init succeeded unexpectedly\n"); return 1; @@ -90,8 +88,7 @@ int main(void) return 1; } - ret = unix_msg_init(&addr2, funcs, 256, 1, - recv_cb, &state, &ctx2); + ret = unix_msg_init(&addr2, funcs, 256, recv_cb, &state, &ctx2); if (ret != 0) { fprintf(stderr, "unix_msg_init failed: %s\n", strerror(ret)); -- cgit