![[BACK]](/icons/back.gif){kind=icon}
Up to [local] / src / usr.sbin / ldpd
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.10, Wed May 26 16:44:32 2010 UTC (14 years ago) by nicm
Branch: MAIN
CVS Tags: HEAD
Changes since 1.9: +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.9 / (download) - annotate - [select for diffs], Wed May 26 13:56:07 2010 UTC (14 years ago) by nicm
Branch: MAIN
Changes since 1.8: +11 -11 lines
Diff to previous 1.8 (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.8 / (download) - annotate - [select for diffs], Wed Apr 7 18:09:39 2010 UTC (14 years, 1 month ago) by nicm
Branch: MAIN
Changes since 1.7: +2 -2 lines
Diff to previous 1.7 (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.7 / (download) - annotate - [select for diffs], Sat Aug 8 18:33:40 2009 UTC (14 years, 9 months ago) by nicm
Branch: MAIN
CVS Tags: OPENBSD_4_7_BASE,
OPENBSD_4_7
Changes since 1.6: +6 -3 lines
Diff to previous 1.6 (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.6 / (download) - annotate - [select for diffs], Mon Jun 8 08:30:06 2009 UTC (14 years, 11 months ago) by dlg
Branch: MAIN
CVS Tags: OPENBSD_4_6_BASE,
OPENBSD_4_6
Changes since 1.5: +4 -11 lines
Diff to previous 1.5 (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.5 / (download) - annotate - [select for diffs], Sun Jun 7 05:56:25 2009 UTC (14 years, 11 months ago) by eric
Branch: MAIN
Changes since 1.4: +15 -3 lines
Diff to previous 1.4 (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.4 / (download) - annotate - [select for diffs], Sun Jun 7 00:40:46 2009 UTC (14 years, 11 months ago) by eric
Branch: MAIN
Changes since 1.3: +11 -3 lines
Diff to previous 1.3 (colored)
Make the imsg protocol network-safe. ok pyr@
Revision 1.3 / (download) - annotate - [select for diffs], Sat Jun 6 22:11:25 2009 UTC (14 years, 11 months ago) by eric
Branch: MAIN
Changes since 1.2: +4 -3 lines
Diff to previous 1.2 (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.2 / (download) - annotate - [select for diffs], Sat Jun 6 08:09:43 2009 UTC (14 years, 11 months ago) by pyr
Branch: MAIN
Changes since 1.1: +106 -33 lines
Diff to previous 1.1 (colored)
make ldpd imsg-in-a-lib ready too.
Revision 1.1 / (download) - annotate - [select for diffs], Mon Jun 1 20:59:45 2009 UTC (15 years ago) by michele
Branch: MAIN
Welcome ldpd, the Label Distribution Protocol daemon. Built using the imsg/three process framework, its main aim is to redistribute MPLS labels between peers. Right now it has some really basic functionalities, the basic protocol works and peers are able to exchange labels and insert them in the kernel. It still does not react to changes of topology. Not yet connected to the builds. ok claudio@ deraadt@