Gleb Smirnoff 2df050ad10 In the splnet(9) times netgraph(4) was synchronous and if a message ... had been replied, the reply was always delivered to the originator synchronously. With introduction of netgraph item callbacks and a wait channel with mutex in ng_socket(4), we have fixed the problem with ngctl(8) returning earlier than the command has been proceeded by target node. But still ngctl(8) can return prior to the reply has arrived to its node. To fix this: - Introduce a new flag for netgraph(4) messages - NGM_HASREPLY. This flag is or'ed with message like NGM_READONLY. - In netgraph userland library if we have sent a message with NGM_HASREPLY flag, then select(2) until reply comes. - Mark appropriate generic commands with NGM_HASREPLY flag, gathering them into one enum {}. Bump generic cookie.		2006-01-12 19:14:40 +00:00
..
debug.c	Recognize all current standard node types.	2005-10-25 20:58:30 +00:00
internal.h
Makefile	Bump the shared library version number of all libraries that have not	2005-07-22 17:19:05 +00:00
msg.c	In the splnet(9) times netgraph(4) was synchronous and if a message	2006-01-12 19:14:40 +00:00
netgraph.3	Yes, NgRecvAsciiMsg has the same results as NgRecvAsciiMsg, but it's	2004-07-04 04:03:37 +00:00
netgraph.h	- Added three new interfaces, NgAllocRecvMsg(), NgAllocRecvAsciiMsg(),	2004-01-27 20:25:14 +00:00
sock.c	Make this compile with GCC4 by fixing a few signedness related warnings.	2005-04-26 14:25:11 +00:00