Date: Mon, 5 Jun 1995 16:05:34 -0700 (PDT) From: pete@pelican.com (Pete Carah) To: bugs@FreeBSD.org Subject: TTYHOG still... Message-ID: <m0sIlDC-000K0hC@pelican.com>
index | next in thread | raw e-mail
PLEASE PLEASE (OK, wait for release, maybe, but it is impossible to run uucp on a fast link as things are) fix TTYHOG to be an option: (or *better*, fix the real problem and make clist sizes dynamic; it is ridiculous to make interactive opens have 16k ttyhog just to get uucp to work on a single port.) At 1024 I can sometimes get errors just from chat setting up a slip call. Yes, I have crtscts set and it does work. I still get the ****** ttyhog error message. Related to this: ***FLAME ON: Also, don't insist in the man page and rc.serial that setting crtscts is an application responsibility; it isn't. It is a hardware consideration and depends entirely on what is connected to the port; the sysadmin knows which ports need it, and the setting needs to apply to everything, even the shell and 'cat', for several. The init+lock device is the right thing, only it is documented rather negatively. The application (in this kind of case) has *no business whatever* knowing what kind of device is connected; it only knows about data streams. ***FLAME OFF -- Pete -------------------------------------------------------------------------- /usr/src/sys/sys/tty.h: #define IBUFSIZ 384 /* Should be >= max value of MIN. */ #define OBUFSIZ 100 +#ifndef TTYHOG #define TTYHOG 1024 +#endif #ifdef KERNEL #define TTMAXHIWAT roundup(2048, CBSIZE) #define TTMINHIWAT roundup(100, CBSIZE) -------------------------------------------------------------home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0sIlDC-000K0hC>