Re: Out of pty's

2003-12-06 Thread Justin Burke
* Lee Harr ([EMAIL PROTECTED]) wrote:
 How do I find out the limit of ptys on my system? (sysctl doesn't
 seem to show anything relevant.)
 
 How do I increase that value? The pseudo-pty value in the kernel config
 has no assigned value (ie. we are using the default) but what is the
 default?
 
 
 Which version of FreeBSD?

4.9-PRERELEASE


 I had a similar problem on my 4.9-stable box. What I did was use
 /dev/MAKEDEV to create some more pty devices.
 
 ls /dev/pty*
 
 will show you how many you have, then
 
 /dev/MAKEDEV pty1   (can also use pty2 pty3 pty4 etc)
 
 will create more.

It seems that creating the devices isn't the problem. I just can't get
screen and ssh to actually use those ptys. I'm going just rebuild the
kernel with modification suggested in the FAQ.


Justin

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Out of pty's

2003-12-06 Thread Justin Burke
* Malcolm Kay ([EMAIL PROTECTED]) wrote:
  1. Build and install a new kernel with the line
 
   pseudo-device pty 256
 
 in the configuration file.
 
  2. Run the commands
 
 
 I believe this may be out of date. I think the kernel may now
 produce 256 by default -- I'm on 4.7-STABLE and more than 32 exist for me.

More than 32 may exist, but can you actually use them? 96 ptys currently
exist on my system, but I can only use 32. The pseudo-device line in my
kernel is the default (ie.  no numeric value is provided).


   # cd /dev
   # sh MAKEDEV pty{1,2,3,4,5,6,7}
 
 to make 256 device nodes for the new terminals.
 
 
 On 4.x certainly need this to create more devices. I don't know if you need to 
 do something with devfs in 5.x, but 5.x doesn't have MAKEDEV.

This seems to be the case on my 5.1 box. The ptys are automatically
created. And the pty limit has been bummed up to 256 in the default
config. (Just checked it with multiple instances of screen)


Justin

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Out of pty's

2003-12-04 Thread Justin Burke
Hi All,

Looks like my system is running out of free pty's. There are a bunch of
users on the system running screen, so we are using up a ton of the
ptys. 

How do I find out the limit of ptys on my system? (sysctl doesn't
seem to show anything relevant.) 

How do I increase that value? The pseudo-pty value in the kernel config
has no assigned value (ie. we are using the default) but what is the
default?


TIA,
Justin

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Out of pty's

2003-12-04 Thread Justin Burke
* Jez Hancock ([EMAIL PROTECTED]) wrote:
 On Thu, Dec 04, 2003 at 01:28:36PM -0800, Justin Burke wrote:
  Looks like my system is running out of free pty's. There are a bunch of
  users on the system running screen, so we are using up a ton of the
  ptys. 
  
  How do I find out the limit of ptys on my system? (sysctl doesn't
  seem to show anything relevant.) 
 I believe you can increase the number of ptys by modifying /etc/ttys -
 from looking at my /etc/ttys file it looks as though once the ttyp* ttys
 are used up, the tty monniker changes to ttyq* etc...
 
  How do I increase that value? The pseudo-pty value in the kernel config
  has no assigned value (ie. we are using the default) but what is the
  default?
 Again I believe this is down to /etc/ttys.


Hi Jez,

/etc/ttys lists a ton of pseudo terminals, which is great. However,
after opening up 32 pseudo terminals (/dev/ptyp[0-9] and
/dev/ptyp[a-v]]), none of the other terminals are used (eg. /dev/ptyq*).
How do I get the system to start using those devices?

(The /etc/ttys entries for /dev/ttyp* are identical to the /dev/ttyq*
entries.)


Justin

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Adding defaultroute

2002-12-16 Thread Justin Burke
I'm having trouble getting a dual-homed system to setup the default
route correctly on bootup. Here are the relevant lines from my rc.conf:

ifconfig_rl0=inet xx.xx.xx.xxx  netmask 255.255.255.0
ifconfig_xl0=DHCP
defaultrouter=xx.xx.xx.x

During bootup, the system enables the default route to go through the xl0
card, which I don't want; I'd like to enable to default route to go
through the rl0 card.

After the network cards are setup, here is what is printed to the
console:

route: writing to routing socket: File exists
add net default: gateway xx.xx.xx.xx: File exists

Any suggestions?

Justin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message