Searched hist:14443 (Results 1 - 14 of 14) sorted by relevance
/freebsd-9.3-release/usr.bin/talk/ | ||
H A D | Makefile | diff 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 D | get_addrs.c | diff 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 D | msgs.c | diff 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 D | talk.h | diff 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 D | ctl.c | diff 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 D | get_iface.c | 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 D | invite.c | diff 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 D | look_up.c | diff 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 D | talk.c | diff 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 D | ctl_transact.c | diff 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 D | display.c | diff 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 D | get_names.c | diff 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 D | init_disp.c | diff 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 D | io.c | diff 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