: FWIW, I think only a fool would want a computer to NOT drop dead connections.
: Any connection that doesn't respond after 8 $^! tries spaced FAR apart
does
: NOT deserve to stay.
:
:If they are spaced too far apart, it is possible for perfectly
:legitimate connections to get shot down as a
:
: If they are spaced too far apart, it is possible for perfectly
: legitimate connections to get shot down as a result of external
: periodicities. (Does somebody's router reset every day at 2:45? If
: so, better hope no keepalives are scheduled for then!)
:
:But remember that the idea is the
Most KDE programs, including the configure scripts, look for the
KDEDIR environment variable. I believe that the correct thing to do
with FreeBSD's KDE install is to set KDEDIR to /usr/local. I do this
in /etc/profile and /etc/csh.cshrc here. (I have KDE in
/usr/local/kde here, too, so I
: wouldn't notice... nobody would notice.
:
:I would. I have several long-lived connections, with a few of them
:are sometimes unreachable for quote some time. I like that they survive,
:and would hate it, if some brain-dead default would ruin my perfectly
:set up connections.
:
:Even more,
:On Sat, 5 Jun 1999 20:13:56 -0400 (EDT), Brian Feldman gr...@unixhelp.org
said:
:
: If they are spaced too far apart, it is possible for perfectly
: legitimate connections to get shot down as a result of external
: periodicities. (Does somebody's router reset every day at 2:45? If
: so, better
:
: 4. It would be desirable to have per socket timeouts, but would
: require application changes which are unlikely to happen.
:
:Huh? I was just considering writing the patch for this. What
:application problems would this create?
:
:The worst thing I can see is that it would mean that
:On Sat, Jun 05, 1999 at 07:37:57AM +0200, Poul-Henning Kamp wrote:
: QED: The following patch.
:[...]
: +tcp_keepalive=YES # Kill dead TCP connections (or NO).
:
:I still don't understand why you insist on making it YES by default. It
:works fine like it is for most of the people right
From: Matthew Dillon dil...@apollo.backplane.com
Subject: Re: net.inet.tcp.always_keepalive on as default ?
Date: Sat, 5 Jun 1999 23:20:20 -0700 (PDT)
Message-ID: 199906060620.xaa17...@apollo.backplane.com
dillon As far as dial-on-demand goes, that also makes no real difference.
dillon
:Huh? I was just considering writing the patch for this. What
:application problems would this create?
:
:The worst thing I can see is that it would mean that changing the
:timeout value on a running system wouldn't affect already opened
:sockets. Even that may be changable by an external
The poor sod in this situation deserves something untoward,
IMNSHO. Protocols like ssh do send something periodically whereas
telnet doesn't. Telnet is a well-known security problem. As others
have pointed out, this is an endemic problem in applications
generally speaking, where a long-term
made cvsupworld last night, when i config the GENERIC kernel :
options.i386: Duplicate option FDC_DEBUG.
.==
Tomer Weller
s...@i.am
well...@netvision.net.il
Drugs are good, and if you do'em
pepole think that you're cool, NoFX
To Unsubscribe: send mail
On 6 Jun 1999, Joel Ray Holveck wrote:
I just noticed (kernelworld from friday) that locate always cores
dump:
$ locate xxx
Segmentation fault (core dumped)
The problem disappears if I recompile locate without the -DMMAP
option.
Running on the very latest
Console: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS drive D: is disk2
FreeBSD/i386 bootstrap loader, Revision 0.7 636/65472kB
(ti...@cicely5.cicely.de, Sun Jun 6 11:28:23 CEST 1999)
Loading /boot/defaults/loader.conf
/kernel text=0x15111d data=0x1b70c+0x240e0
New kernel won't build on current.
when I do a config kernelname
I get : options.i386: Duplicate option FDC_DEBUG.
If i comment out the following from options.i386
everything builds.
#FDC_DEBUG opt_fdc.h
#FDC_YE opt_fdc.h
Manfred
=
||
Subject says it all.. Almost..
Is it natd or is it the kernel ??
Maybe a plug-in system for natd could do it ?
---
Nicolai Petri
n...@swamp.dk
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Hi,
just today I got this error, never had it before in all those
months I have been tracking CURRENT now.
Jun 6 17:15:26 daemon /kernel: sio0: 65 more tty-level buffer overflows
(total 65)
Jun 6 17:15:28 daemon /kernel: sio0: 131 more tty-level buffer overflows
(total 196)
Jun 6 17:15:29
Hi,
--
elf make world started on Sun Jun 6 19:55:14 BST 1999
elf make world completed on Sun Jun 6 19:55:15 BST 1999
--
Given that this is just cosmetic sugar (and IMHO
On Sat, Jun 05, 1999 at 11:26:28PM -0700, Matthew Dillon wrote:
If the poor sod hasn't touched his xterm for 8 days, he's either dead
or he doesn't care if it goes away.
Thanks for your concern.
Matt, poor sod.
--
Matthew Hunt m...@astro.caltech.edu * UNIX is a lever for the
I don't get you. We did get it right and it works fine. If you
change your date in the middle then it can't help you, nor can it
help you if the world build completely fails in the middle or
something. :)
- Jordan
--
elf make world
ECOTECH TECHNOLOGIES, L.L.C.
4001 E., Broadway Road, Suite 7, Phoenix, AZ 85040, USA
Tel: (602) 437 8000, Fax: (602) 437 4033
E-mail: ecotech...@yahoo.com
fixed..
I originally used STARTTIME!=date
and someone confused me into using STARTTIME?=`date`
but I forgot that they get evaluated at different times.
On Sun, 6 Jun 1999, Jordan K. Hubbard wrote:
I don't get you. We did get it right and it works fine. If you
change your date in the middle
fixeed (My braino)
On Sun, 6 Jun 1999, Bob Bishop wrote:
Hi,
--
elf make world started on Sun Jun 6 19:55:14 BST 1999
elf make world completed on Sun Jun 6 19:55:15 BST 1999
Lookup natd on the freebsd page.
On Sun, 6 Jun 1999, Nicolai Petri wrote:
Subject says it all.. Almost..
Is it natd or is it the kernel ??
Maybe a plug-in system for natd could do it ?
---
Nicolai Petri
n...@swamp.dk
To Unsubscribe: send mail to majord...@freebsd.org
with
At 12:49 pm -0700 6/6/99, Jordan K. Hubbard wrote:
I don't get you. We did get it right and it works fine. If you
change your date in the middle then it can't help you, nor can it
help you if the world build completely fails in the middle or
something. :)
No, really, only the subject line is in
Sorry, I wasn't aware of the fact that Julian had broken this since
my last make world. :)
- Jordan
At 12:49 pm -0700 6/6/99, Jordan K. Hubbard wrote:
I don't get you. We did get it right and it works fine. If you
change your date in the middle then it can't help you, nor can it
help you
redwood201:/usr/src/sys/i386/conf#config -g DUSTER
options.i386: Duplicate option FDC_DEBUG.
redwood201:/usr/src/sys/i386/conf#grep FDC_DEBUG *
LINT:# FDC_DEBUG enables floppy debugging. Since the debug output is
huge, you
LINT:optionsFDC_DEBUG
options.i386:FDC_DEBUG
This option is in /sys/conf/options and /sys/i386/conf/options.i386
According to the cvs log, the floppy driver has moved out of the i386
architecture directory. It seems the options.i386 has been forgotten
(options.pc98 has been corrected).
Daniel
Alex Zepeda schrieb:
At 1:28 pm -0700 6/6/99, Julian Elischer wrote:
it's there because it removes a whole step in finding out how long
the compile took. (for example if you forget to redirect your output to a
log file (like I did yesterday :-))
I use a wrapper script which backgrounds the build and redirects the
Is there anything in current that provides wide character support? I'm
messing around with document formatting, and I have to be involved with
wide character things. One example: wcscat(). It's not the only one, I
just need to know if it's in *any* library, and declared in any include
file.
Is there anything in current that provides wide character support? I'm
messing around with document formatting, and I have to be involved with
wide character things. One example: wcscat(). It's not the only one, I
just need to know if it's in *any* library, and declared in any include
On Sat, Jun 05, 1999 at 09:08:54PM +0300, Tomer Weller wrote:
every small kde program i try to install (right now i tried Knewmail and
Kover)
i get :
checking for kde headers installed... configure: error: your system is not
able to compile a small KDE application!
Check, if you installed
Is there anything in current that provides wide character support? I'm
messing around with document formatting, and I have to be involved with
wide character things. One example: wcscat(). It's not the only one, I
just need to know if it's in *any* library, and declared in any include
There are several Japanese people working on stateful multibyte char
support. Existing codebase like glibc only supports stateless
multibyte char. People using iso-2022 variants (Japan, Korea,
China, you name it) need stateful multibyte char support.
We have
I was wondering, I've been spending all my time recently on a research
task, and I might have missed this: I just rebuilt world, then
reinstalled a new kernel, and it won't mount root. Luckily, my old
kernel is just fine, and uses my new modules fine, but it won't mount
root. I noticed in the
But remember that the idea is the keepalive would keep trying for a
certain amount of time, and this would be finely configureable.
Adjusting the keepalive's retry period after activation is also
irrelevant. As they currently stand, keepalives operate in virtually
[snip]
I don't see why
Joel Ray Holveck jo...@gnu.org wrote:
I don't see why this is a point of discussion. The keepalive timers
are all configurable via sysctl.
Not quite all. The variables tcp_keepcnt and tcp_maxpersistidle are
not accessible via sysctl (the latter is not directly related to the
current keepalives
On Mon, 7 Jun 1999, Jun-ichiro itojun Hagino wrote:
Is there anything in current that provides wide character support? I'm
messing around with document formatting, and I have to be involved with
wide character things. One example: wcscat(). It's not the only one, I
just need to know
Don't wory. I guess with my dual controllers, that's likely what did
it. I only had ahc0, not ahc1, in my config file. For some reason, it
didn't like that anymore.
Anyhow, it's fixed.
+---
Chuck Robey |
k...@lyris.com wrote:
Lookup natd on the freebsd page.
Yes, and take a look at the ipfw 'forward' rule. It is your friend.
Thomas
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
The latest snapshot can be grabbed from:
http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz
New in this release...
1) Man pages (I don't think I included them prior to this)
2) Makefile that sorta works (makes a dynamic library.. I don't recommend
people use the dynamic
Do you guys have any testable, even if it's not ready for prime time? I
need wchar.h and the wcs* functions for a project for FreeBSD. You want
me to have this, I think. David said he had something ready to play
with (I think) but I haven't heard from him yet.
We have some code
41 matches
Mail list logo
