![[BACK]](/icons/back.gif){kind=icon}
Up to [local] / src / usr.sbin / dvmrpd
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.11, Wed May 26 16:44:32 2010 UTC (14 years ago) by nicm
Branch: MAIN
CVS Tags: HEAD
Changes since 1.10: +1 -1 lines
FILE REMOVED
Move imsg into libutil and add a man page. Minor bump for libutil. Previous versions of this diff and man page looked at by various people. "you should just commit" deraadt
Revision 1.10 / (download) - annotate - [select for diffs], Wed May 26 13:56:07 2010 UTC (14 years ago) by nicm
Branch: MAIN
Changes since 1.9: +11 -11 lines
Diff to previous 1.9 (colored)
Rename some imsg bits to make namespace collisions less likely buf to ibuf, buf_read to ibuf_read, READ_BUF_SIZE to IBUF_READ_SIZE. ok henning gilles claudio jacekm deraadt
Revision 1.9 / (download) - annotate - [select for diffs], Wed Apr 7 18:09:39 2010 UTC (14 years, 2 months ago) by nicm
Branch: MAIN
Changes since 1.8: +2 -2 lines
Diff to previous 1.8 (colored)
Remove XXX comment and just close received fd if calloc() fails. If this happens the imsg may no longer be usable as there may be queued messages, but this is a) already the case with the code now, and b) would be the case if recvmsg() fails anyway, so we can document that -1 from imsg_read() invalidates the struct imsgbuf. discussed with and ok eric
Revision 1.8 / (download) - annotate - [select for diffs], Sat Aug 8 18:33:40 2009 UTC (14 years, 10 months ago) by nicm
Branch: MAIN
CVS Tags: OPENBSD_4_7_BASE,
OPENBSD_4_7
Changes since 1.7: +6 -3 lines
Diff to previous 1.7 (colored)
Make imsg_clear close and free any fds in the received fd queue as well as freeing the msgbuf. While here also remove an unnecessary while loop. ok eric pyr
Revision 1.7 / (download) - annotate - [select for diffs], Mon Jun 8 08:30:06 2009 UTC (15 years ago) by dlg
Branch: MAIN
CVS Tags: OPENBSD_4_6_BASE,
OPENBSD_4_6
Changes since 1.6: +4 -11 lines
Diff to previous 1.6 (colored)
revert this change by eric@: Make the imsg protocol network-safe. it might be network safe, but half the imsg based daemons on my firewalls dont run anymore.
Revision 1.6 / (download) - annotate - [select for diffs], Sun Jun 7 05:56:25 2009 UTC (15 years ago) by eric
Branch: MAIN
Changes since 1.5: +15 -3 lines
Diff to previous 1.5 (colored)
Change the way fds passed over a socket are retreived on the receiving side. Currently the receiver fetches an imsg via imsg_get() and if he expects an fd, he then calls imsg_get_fd() to fetch the next fd queued on the imsgbuf from which the imsg came. This changes hides the fd queueing mechanism to the API user. When closing an imsg with an fd, the message is flagged so that the receiving end knows it must dequeue the fd in imsg_get() and return it with the imsg structure. This way there is no (less) possible screw up from imsg_get_fd() not being called directly after imsg_get() by the user. The retreived imsg is self-contained. ok pyr@, "I like that" henning@
Revision 1.5 / (download) - annotate - [select for diffs], Sun Jun 7 00:40:46 2009 UTC (15 years ago) by eric
Branch: MAIN
Changes since 1.4: +11 -3 lines
Diff to previous 1.4 (colored)
Make the imsg protocol network-safe. ok pyr@
Revision 1.4 / (download) - annotate - [select for diffs], Sat Jun 6 22:11:25 2009 UTC (15 years ago) by eric
Branch: MAIN
Changes since 1.3: +4 -3 lines
Diff to previous 1.3 (colored)
change the imsg header fields a bit to prepare for upcoming changes. add a flag field, use u_int32_t for pid_t and extend type to 32 bits for padding. ok pyr@
Revision 1.3 / (download) - annotate - [select for diffs], Sat Jun 6 07:52:04 2009 UTC (15 years ago) by pyr
Branch: MAIN
Changes since 1.2: +112 -36 lines
Diff to previous 1.2 (colored)
make dvmrpd imsg-in-a-lib ready as well. ``put it in'' claudio@, ok eric@
Revision 1.2 / (download) - annotate - [select for diffs], Mon Mar 19 10:13:20 2007 UTC (17 years, 2 months ago) by henning
Branch: MAIN
CVS Tags: OPENBSD_4_5_BASE,
OPENBSD_4_5,
OPENBSD_4_4_BASE,
OPENBSD_4_4,
OPENBSD_4_3_BASE,
OPENBSD_4_3,
OPENBSD_4_2_BASE,
OPENBSD_4_2
Changes since 1.1: +2 -2 lines
Diff to previous 1.1 (colored)
do not signal "connection closed" upstream on EINTR/EAGAIN, from bgpd et al
Revision 1.1 / (download) - annotate - [select for diffs], Thu Jun 1 14:12:20 2006 UTC (18 years ago) by norby
Branch: MAIN
CVS Tags: OPENBSD_4_1_BASE,
OPENBSD_4_1,
OPENBSD_4_0_BASE,
OPENBSD_4_0
Welcome dvmrpd started by Esben Norby some time ago by using the imsg/three process framework of ospfd. Right now it is not particularly useful, major parts are still missing but is imported to allow more people to work on it. Status: The IGMP part is mostly complete, allowing clients to join and leave groups. Election the IGMP querier of a network is also functional, only thing missing is some corner cases when going from non-querier to querier. About half of the DVMRP is functional, probes and route reports are functional. Multicast streams can be detected and the MFC can be manipulated. The RIB is not complete but operational. Not yet connected to the builds. OK claudio@