George Hartzell wrote:
===> games/fortune/strfile
/usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for
/usr/src/games/fortune/strfile
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include
/usr/src/games/fortune/strfile/strfile.c
echo strfil
Christopher Nehren wrote:
I think I did only "make world" without DESTDIR and specified it of
course afterwards when doing "make installworld".
"make world" builds and installs the world onto your current system,
leaving a /usr/obj intact. Unless you specified a DESTDIR for the
installworld, it wa
George Hartzell wrote:
Can anyone suggest a way forward?
I think I did only "make world" without DESTDIR and specified it of
course afterwards when doing "make installworld".
Greetings,
Robert!
___
freebsd-questions@freebsd.org mailing list
http://lists
Charles Swiger wrote:
If the TCP connection is in FIN_WAIT_2, FreeBSD may send out ACKs
periodicly, trying to nudge the other side to send a FIN to finish
closing the connection.
This is indeed the case (when I interpret the tcpdump output correct):
21:19:20.139373 IP HTTP_SERVER.http > HTTP_CLIE
Charles Swiger wrote:
FIN_WAIT_2 is a name describing the state of a TCP connection. It's
defined in a state diagram in RFC-793. But otherwise, your description
is pretty good:
[ ... ]
| CLOSE +-+
| --- | ESTAB |
| snd FIN
Charles Swiger wrote:
The TCP stack wants the remote end to acknowledge the last FIN it sends
and close the connection cleanly, and there is a timer (2 * MSL?) which
gets started when a connection moves into the closing stages
(FIN_WAIT_1, FIN_WAIT_2, LAST_ACK).
So FIN_WAIT_2 is the time the ser
I have set up a webserver behind a bridged firewall, something like:
INTERNET - FIREWALL - WEBSERVER
The webserver is running FreeBSD, and currently I get many FIN_WAIT_2
states:
# netstat -n -p tcp | grep FIN_WAIT_2 | wc -l
48
I wonder WHAT is responsible for sending every 5
