Searched hist:14443 (Results 1 - 14 of 14) sorted by relevance

/freebsd-9.3-release/usr.bin/talk/
H A DMakefilediff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dget_addrs.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dmsgs.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dtalk.hdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dctl.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dget_iface.c14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dinvite.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dlook_up.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dtalk.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dctl_transact.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Ddisplay.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dget_names.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dinit_disp.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example
H A Dio.cdiff 14443 Sat Mar 09 17:23:01 MST 1996 joerg Make talk automagically find out the interface IP address where the
remote peer will be connected through. This avoids the ``Checking for
invitation on caller's machine'' problem for multi-homed hosts.

Thanks to: Garrett, for his `find_interface' example

Completed in 178 milliseconds