{section: These pages are outdated outrageously. Do not believe anything written here}
{section: Introduction}
-This page is work note of converting Condor to IPv6 compatible. More precisely, IPv4/IPv6 both compatible.
+This page is work note of converting HTCondor to IPv6 compatible. More precisely, IPv4/IPv6 both compatible.
{section: What should be changed?}
@@ -34,7 +34,7 @@
{section: ...}
-Condor's utility function that returns or accepts sockaddr_in directly. These functions will be converted if we change top-level functions (listed above).
+HTCondor's utility function that returns or accepts sockaddr_in directly. These functions will be converted if we change top-level functions (listed above).
{code}
@@ -61,8 +61,8 @@
Printing IP address to log file should be considered since existing layout may not work well.
-{section: Current Condor Code Base}
-As noted earlier, Condor source has 576 lines that uses obsolete BSD functions.
+{section: Current HTCondor Code Base}
+As noted earlier, HTCondor source has 576 lines that uses obsolete BSD functions.
What makes problem complicated is that unsigned long is used to hold IP address. There are many places to change. For example, in sock.h,{linebreak}
{code}
@@ -165,9 +165,9 @@
Let's find a way to configure it. It may be done by using "configure" script.
-{section: Condor NO_DNS option}
+{section: HTCondor NO_DNS option}
-In Condor, NO_DNS option eliminates its dependency to Domain Name System. According to condor_netdb.c
+In HTCondor, NO_DNS option eliminates its dependency to Domain Name System. According to condor_netdb.c
{code}
/* SPECIAL NAMES:
@@ -207,7 +207,7 @@
My initial plan is to place prefix "condor_". inet_ntop becomes condor_inet_ntop. connect becomes condor_connect.
-There are some functions that already has these kind of name such as condor_inet_ntoa() in internet.c. It seems these already existing condor-specific functions are obsolete, either. Thus, we may remove or convert existing condor_ prefixed socket functions.
+There are some functions that already has these kind of name such as condor_inet_ntoa() in internet.c. It seems these already existing HTCondor-specific functions are obsolete, either. Thus, we may remove or convert existing condor_ prefixed socket functions.
I do not think we need any class that encapsulating those BSD socket interfaces. The reason is that I do not change any semantics of BSD socket interface but only syntax.
@@ -258,7 +258,7 @@
Converting existing code to call getaddrinfo() is not trivial as I expected. This function returns addrinfo structure which embeds sockaddr*. Since it is not sockaddr_in(IPv4 address), the caller must check sockaddr::sin_family to see whether it belongs to IPv4 or IPv6 address.
-Currently, no Condor source codes call getaddrinfo directly.
+Currently, no HTCondor source codes call getaddrinfo directly.
One possible way to deal with getaddrinfo() is that define condor_addrinfo that contains IpAddr class instead of sockaddr struct. So, the proxy function may convert addrinfo to condor_addrinfo. It involves changing sockaddr_in to IpAddr class(which is actually sockaddr_in6). However, I am unsure about this unnecessary memory copies and type changes.
@@ -405,7 +405,7 @@
*:why do you call <a.b.c.d:pppp> as sinful string? what does it mean 'sinful'? - Now that I know.
-This is Condor specific term. We need to extend definition to include IPv6 address. For example, <[a:b:c:d:e:f:g:h]:pppp> would work.
+This is HTCondor specific term. We need to extend definition to include IPv6 address. For example, <[a:b:c:d:e:f:g:h]:pppp> would work.
*:do we really need unified ip address class? IPv6 address space contains IPv4 and there is 1-to-1 mapping.
