"4c69e7b9d569647edcbb5f125efcfbc6217b2440" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"4 c69e7b9d569647edcbb5f125efcfbc6217b2440" (Results 1 – 4 of 4) sorted by relevance

/freebsd/usr.sbin/ypserv/
H A D	yp_extern.h	diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner. diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner.
H A D	Makefile	diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner. diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner.
H A D	yp_main.c	diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner. diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner.
H A D	yp_server.c	diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner. diff 4c69e7b9d569647edcbb5f125efcfbc6217b2440 Tue Dec 03 03:37:39 CET 1996 Bill Paul <wpaul@FreeBSD.org> Back out the non-forking YPPROC_ALL stuff. Whatever drugs I was doing when I came up with this idea weren't strong enough to help me see it through. If this was a self-contained application and I had complete control over what data got sent through what socket and when, I might be able to get everything to work right without blocking, but instead I have RPC/XDR in between me and the socket layer, and they have their own ideas about what to do. Maybe one day I'll go totally mad and figure out the right way to do this; in the meantime this mess goes on the back burner.