public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karl Tatgenhorst <ketatgenhorst@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: [lkml] pseudo tty / kernel compile question
Date: Sat, 24 Jan 2004 00:16:48 -0600	[thread overview]
Message-ID: <40120DD0.7090802@comcast.net> (raw)
In-Reply-To: <20040113172441.C7256@flint.arm.linux.org.uk>

Hi,

I have read the FAQ and have searched heartily for anything which I 
could understand about this, but have come up empty. I am replacing a 
Unixware 7.1.1 server (not a unixware question) with RH ES3. The server 
hosts a BASIC application so users log in via ssh sessions. The problem 
is I am getting to around 120 users and then getting a no pseudo ttys 
available. RH support had me bump up the number of instances in 
xinetd.conf which did nothing. Then a person we use for Unix support 
said that the type of pseudo ttys that we use is wrong. His example:

when I log in over ssh I get /dev/pts/0 when I type tty. But he says it 
should be of type /dev/ptsp* I know (suspect strongly) that this is 
configured in the kernel but not where. Can anyone please post a little 
information for me regarding this.

I heartily welcome your assistance in smiting this unixware servers job.

Karl Tatgenhorst

PS if it is not too much further trouble, please CC any responses to 
ktatgenhorst@eiltd.com

Thanks one and all


  reply	other threads:[~2004-01-24  6:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 11:00 [PROBLEM] ircomm ioctls Jozef Vesely
2004-01-13 11:36 ` Russell King
2004-01-13 11:49   ` Outstanding fixups (was: Re: [PROBLEM] ircomm ioctls) Russell King
2004-01-13 17:15     ` Russell King
2004-01-13 17:24       ` [1/3] Serial fixups (mostly tested) Russell King
2004-01-24  6:16         ` Karl Tatgenhorst [this message]
2004-01-25 21:53           ` [lkml] pseudo tty / kernel compile question David Woodhouse
2004-01-13 17:33       ` [2/3] Russell King
2004-01-13 17:55         ` [2/3] Henrique Oliveira
2004-01-13 18:53           ` [2/3] John Stoffel
2004-01-13 22:15         ` [2/3] Paul Mackerras
2004-01-14  7:01           ` [2/3] Benjamin Herrenschmidt
2004-01-16 11:34             ` [2/3] Matthias Urlichs
2004-01-16  0:54         ` [2/3] Greg KH
2004-01-18 12:43         ` [2/3] Greg Ungerer
2004-01-18 15:42           ` [2/3] Russell King
2004-01-18 23:23             ` [2/3] Greg Ungerer
2004-01-13 17:42       ` [3/3] 2.6 broken serial drivers Russell King
2004-01-13 20:21         ` Andrew Morton
2004-01-13 21:10           ` Russell King
2004-01-18 16:16             ` Russell King
2004-01-14 12:42         ` Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40120DD0.7090802@comcast.net \
    --to=ketatgenhorst@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox