Re: How to enable more than 256 pty's?
"Steven Hartland" <[EMAIL PROTECTED]> writes: > Thanks for the tip there but I cant find any function called pty_create_slave > in the source. Just grep your source tree for occurrences of pqrsPQRS. > Is this something that's possible on 5.x / 6.2 or something that will need a > lot of work? It shouldn't be any harder on 5.x / 6.x than on 7.x. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Promise SATA300/TX4 and SATA DVD
Jeremy Chadwick wrote: On Tue, Oct 02, 2007 at 03:07:28PM -0400, Keith Mitchell wrote: I'm running 6.2-STABLE from about 2 weeks ago. I looked and didn't see any ata driver updates so I think I have the latest on the RELENG_6 tree. I also booted in verbose mode and didn't see anything too obvious but the messages are below... Does the driver for this card not support atapi devices? If I remember correctly, the present ATA driver in RELENG_6 does not support ATAPI devices on SATA. CURRENT is supposed to. This drive works on other controller cards just fine :-) I know it isn't supported in 6.2 but 6.2-STABLE does work at least on some controllers. I know for a fact it works on the SiL 3114 and Intel ICH8 controllers... Just not on this promise card.. (the Intel ICH8 is on a different machine running the same vintage of 6.2-STABLE... the SiL 3114 is from this very machine and version of 6.2-STABLE... that controller has other issues for me though). -- Keith Mitchell Email: [EMAIL PROTECTED]PGP key available upon request ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Promise SATA300/TX4 and SATA DVD
On Tue, Oct 02, 2007 at 03:07:28PM -0400, Keith Mitchell wrote: > I'm running 6.2-STABLE from about 2 weeks ago. I looked and didn't see any > ata driver updates so I think I have the latest on the RELENG_6 tree. I > also booted in verbose mode and didn't see anything too obvious but the > messages are below... Does the driver for this card not support atapi > devices? If I remember correctly, the present ATA driver in RELENG_6 does not support ATAPI devices on SATA. CURRENT is supposed to. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel Fatal trap 12 on 6.2 release p7 how to report it
On Tue, Oct 02, 2007 at 02:55:08PM -0500, Natham wrote: > Hi: > > Im getting a Fatal trap 12 from a freebsd 6.2 release p7, how can i > report it and get help?? Check http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html on how to obtain needed information. -- Yuri Pankov <[EMAIL PROTECTED]> ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel Fatal trap 12 on 6.2 release p7 how to report it
Hi: Im getting a Fatal trap 12 from a freebsd 6.2 release p7, how can i report it and get help?? Oct 2 02:39:37 freebsd kernel: Oct 2 02:39:37 freebsd kernel: Oct 2 02:39:37 freebsd kernel: Fatal trap 12: page fault while in kernel mode Oct 2 02:39:37 freebsd kernel: cpuid = 0; apic id = 00 Oct 2 02:39:37 freebsd kernel: fault virtual address = 0x28 Oct 2 02:39:37 freebsd kernel: fault code = supervisor read, page not present Oct 2 02:39:37 freebsd kernel: instruction pointer = 0x20:0xc06af070 Oct 2 02:39:37 freebsd kernel: stack pointer = 0x28:0xcbf5fc2c Oct 2 02:39:37 freebsd kernel: frame pointer = 0x28:0xcbf5fc34 Oct 2 02:39:37 freebsd kernel: code segment= base 0x0, limit 0xf, type 0x1b Oct 2 02:39:37 freebsd kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 2 02:39:37 freebsd kernel: processor eflags= interrupt enabled, resume, IOPL = 0 Oct 2 02:39:37 freebsd kernel: current process = 5 (thread taskq) Oct 2 02:39:37 freebsd kernel: trap number = 12 Oct 2 02:39:37 freebsd kernel: panic: page fault Oct 2 02:39:37 freebsd kernel: cpuid = 0 Oct 2 02:39:37 freebsd kernel: Uptime: 47m51s Oct 2 02:39:37 freebsd kernel: Cannot dump. No dump device defined. Oct 2 02:39:37 freebsd kernel: Automatic reboot in 15 seconds - press a key on the console to abort Oct 2 02:39:37 freebsd kernel: Rebooting... - Oct 2 14:32:00 freebsd kernel: Fatal trap 12: page fault while in kernel mode Oct 2 14:32:00 freebsd kernel: cpuid = 0; apic id = 00 Oct 2 14:32:00 freebsd kernel: fault virtual address = 0x28 Oct 2 14:32:00 freebsd kernel: fault code = supervisor read, page not present Oct 2 14:32:00 freebsd kernel: instruction pointer = 0x20:0xc06911c8 Oct 2 14:32:00 freebsd kernel: stack pointer = 0x28:0xcbf62c2c Oct 2 14:32:00 freebsd kernel: frame pointer = 0x28:0xcbf62c34 Oct 2 14:32:00 freebsd kernel: code segment= base 0x0, limit 0x f, type 0x1b Oct 2 14:32:00 freebsd kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 2 14:32:00 freebsd kernel: processor eflags= interrupt enabled, res ume, IOPL = 0 Oct 2 14:32:00 freebsd kernel: current process = 5 (thread taskq) Oct 2 14:32:00 freebsd kernel: trap number = 12 Oct 2 14:32:00 freebsd kernel: panic: page fault Oct 2 14:32:00 freebsd kernel: cpuid = 0 Oct 2 14:32:00 freebsd kernel: Uptime: 4h2m1s Oct 2 14:32:00 freebsd kernel: Cannot dump. No dump device defined. Oct 2 14:32:00 freebsd kernel: Automatic reboot in 15 seconds - press a key on the console to abort - FreeBSD freebsd.loc 6.2-RELEASE-p7 FreeBSD 6.2-RELEASE-p7 #1: Tue Oct 2 03:29:14 COT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VIXEN i386 --- i try freebsd-stable and same problem. Where can i report this problem? -- mmm, interesante. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Promise SATA300/TX4 and SATA DVD
I'm trying to get a SATA DVD-ROM drive in an older system (Athlon-XP vintage) and can't seem to get anything that works 100% correct. I've tried connecting the drive to various SiL chipset sata controllers (they have builtin raid0/1) and the card bios sees the drive and freebsd sees the drive fine. But the system bios always tries to boot off of the drive whether there is a drive in there or not. I think this is because these cards list the DVD drive in the bios list before my actual hard drive. So, then I bought a Promise SATA300/TX4 card that doesn't do RAID and it seems to interact with the system bios just fine. But... FreeBSD doesn't detect the DVD drive on the controller even though FreeBSD sees the controller and the card bios sees the drive and can boot off it. I'm running 6.2-STABLE from about 2 weeks ago. I looked and didn't see any ata driver updates so I think I have the latest on the RELENG_6 tree. I also booted in verbose mode and didn't see anything too obvious but the messages are below... Does the driver for this card not support atapi devices? atapci0: port 0xc400-0xc47f,0xc800-0xc8ff mem 0xe9825000-0xe9825fff, 0xe980-0xe981 irq 17 at device 9.0 on pci1 pci1: child atapci0 requested type 4 for rid 0x20, but the BAR says it is an memio atapci0: [MPSAFE] atapci0: Reserved 0x2 bytes for rid 0x20 type 3 at 0xe980 atapci0: Reserved 0x1000 bytes for rid 0x1c type 3 at 0xe9825000 atapci0: [MPSAFE] ata2: on atapci0 ata2: SATA connect ready time=0ms ata2: sata_connect devices=0x1 ata2: [MPSAFE] ata3: on atapci0 ata3: SATA connect status= ata3: [MPSAFE] ata4: on atapci0 ata4: SATA connect status= ata4: [MPSAFE] ata5: on atapci0 ata5: SATA connect status= I think the DVD drive is connected to Port3... not sure how that corresponds to the ATA channels. My gues is that ata2 is where it should be since it mentions "sata connect devices = 0x1". ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
Thanks for the tip there but I cant find any function called pty_create_slave
in the source.
N.B. Machine is running 5.4 but I also looked on 6.2 which we could upgrade
to but still couldn't find it, so I assume you may be talking about something
that's in current which we couldn't risk on this machine.
Is this something that's possible on 5.x / 6.2 or something that will need a
lot of work?
Regards
Steve
- Original Message -
From: "Dag-Erling Smørgrav" <[EMAIL PROTECTED]>
You need to change the way ptys are named in pty_create_slave() and
pty_clone() in sys/kern/tty_pty.c. Just changing names won't help as
the sequence is also hardcoded in pty_clone().
You also need to change grantpt(), openpty() and any other userland code
which has hardcoded knowledge of the naming scheme:
[EMAIL PROTECTED] ~% gfs pqrsPQRS
src/sys/kern/tty_pty.c: static char *names = "pqrsPQRS";
src/sys/kern/tty_pty.c: * pts ==
/dev/tty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
src/sys/kern/tty_pty.c: * ptc ==
/dev/pty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
src/contrib/telnet/telnetd/sys_term.c: for (cp = "pqrsPQRS"; *cp; cp++) {
src/usr.sbin/ac/ac.c: strchr("pqrsPQRS",
usr.ut_line[3]) != 0 ||
src/lib/libutil/pty.c: for (cp1 = "pqrsPQRS"; *cp1; cp1++) {
src/lib/libc/stdlib/grantpt.c: #define PT_DEV1 "pqrsPQRS"
Alternatively, set kern.pts.enable to 1, and find and fix the
hang-on-close bug in the pts code (if it hasn't been fixed already)
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sparc64 kernel build error
On Mon, Oct 01, 2007 at 02:29:54PM +, Matthew Herzog wrote: > Hello Beasties. > > I have attached the error text and my kernel config. The build seems to > die while building ipfilter but I'm guessing that's not the real > reason for it failing. > > Thanks for any suggestions. > > -- Matt H <...> > cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter > -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath -I/usr/src/sys/contrib/ngatm > -I/usr/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include > opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 > --param large-function-growth=1000 -mcmodel=medlow -msoft-float > -ffreestanding -Werror /usr/src/sys/dev/syscons/schistory.c > In file included from /usr/src/sys/dev/syscons/schistory.c:46: > ./machine/sc_machdep.h:71:1: "SC_NORM_ATTR" redefined > In file included from /usr/src/sys/dev/syscons/schistory.c:33: > ./opt_syscons.h:1:1: this is the location of the previous definition > *** Error code 1 > Remove options SC_NORM_ATTR from your kernel config file or if you really ned green on black change sys/sparc64/include/sc_machdep.h to include opt_syscons.h and only define SC_NORM_ATTR etc if they're not already defined. Marius ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
Ed Schouten <[EMAIL PROTECTED]> writes: > This is a known issue IIRC. See line 245 of tty_pts.c 1.16. Can be > easily reproduced by killing the sshd while apps are still running in > the shell. It's not that simple. The question is why t_refcnt > 1 when there are no processes left attached to the tty. I managed to reproduce this as follows: $ script -q 1 script -q 2 script -q 3 script -q 4 tty if nothing else is going on at the same time, you should always see the same output, but instead you see a steadily increasing pts number. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
* Ed Schouten <[EMAIL PROTECTED]> wrote: > * Vlad GALU <[EMAIL PROTECTED]> wrote: > > On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > > > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > > > he can catch up with the thread. > > > > > > Which symptoms? I can no longer reproduce the hang-on-close bug. > > > >Strangely enough, me neither. In his case, allocated pts' wouldn't > > get deallocated once the sessions ended. > > This is a known issue IIRC. See line 245 of tty_pts.c 1.16. Can be > easily reproduced by killing the sshd while apps are still running in > the shell. > > I thought we weren't able to destroy the device there, because you can't > destroy a TTY when it is used by an application (i.e. when it's the > controlling terminal). Thought about this 2 seconds after I sent my message: this is also responsible for the `zombie jails': tty's are made with make_dev_cred, which causes ucred's to be leaked, which eventually causes prisons to be leaked. -- Ed Schouten <[EMAIL PROTECTED]> WWW: http://g-rave.nl/ pgpyE20Dd6QGI.pgp Description: PGP signature
Re: How to enable more than 256 pty's?
On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > > > he can catch up with the thread. > > > Which symptoms? I can no longer reproduce the hang-on-close bug. > > Strangely enough, me neither. In his case, allocated pts' wouldn't get > > deallocated once the sessions ended. > > Wouldn't get deallocated right away, or wouldn't get deallocated at all? > Apparently, it is not unusual for pts reclamation to be delayed a bit by > a non-zero refcnt. > As per my other mail, they wouldn't get deallocated at all. They still show up in /dev/pts/ even after closing, and the next integer index is picked up upon the next terminal creation. > DES > -- > Dag-Erling Smørgrav - [EMAIL PROTECTED] > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
* Vlad GALU <[EMAIL PROTECTED]> wrote: > On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > > he can catch up with the thread. > > > > Which symptoms? I can no longer reproduce the hang-on-close bug. > >Strangely enough, me neither. In his case, allocated pts' wouldn't > get deallocated once the sessions ended. This is a known issue IIRC. See line 245 of tty_pts.c 1.16. Can be easily reproduced by killing the sshd while apps are still running in the shell. I thought we weren't able to destroy the device there, because you can't destroy a TTY when it is used by an application (i.e. when it's the controlling terminal). -- Ed Schouten <[EMAIL PROTECTED]> WWW: http://g-rave.nl/ pgpIkLIgzEu2i.pgp Description: PGP signature
Re: How to enable more than 256 pty's?
On 10/2/07, Vlad GALU <[EMAIL PROTECTED]> wrote: > On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > > he can catch up with the thread. > > > > Which symptoms? I can no longer reproduce the hang-on-close bug. > >Strangely enough, me neither. In his case, allocated pts' wouldn't > get deallocated once the sessions ended. > > However, I see that, if I use pts/0-7, for instance, then log off pts/7, the next assigned pts will be pts/8. Is this expected? I tried lowering kern.pts.max to 20. If I open 20 of them and close them afterwards, on the next try I get "no more ptys" from my screen. > > DES > > -- > > Dag-Erling Smørgrav - [EMAIL PROTECTED] > > > > > -- > If it's there, and you can see it, it's real. > If it's not there, and you can see it, it's virtual. > If it's there, and you can't see it, it's transparent. > If it's not there, and you can't see it, you erased it. > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
"Vlad GALU" <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > > he can catch up with the thread. > > Which symptoms? I can no longer reproduce the hang-on-close bug. > Strangely enough, me neither. In his case, allocated pts' wouldn't get > deallocated once the sessions ended. Wouldn't get deallocated right away, or wouldn't get deallocated at all? Apparently, it is not unusual for pts reclamation to be delayed a bit by a non-zero refcnt. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > "Vlad GALU" <[EMAIL PROTECTED]> writes: > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > he can catch up with the thread. > > Which symptoms? I can no longer reproduce the hang-on-close bug. Strangely enough, me neither. In his case, allocated pts' wouldn't get deallocated once the sessions ended. > > DES > -- > Dag-Erling Smørgrav - [EMAIL PROTECTED] > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
"Vlad GALU" <[EMAIL PROTECTED]> writes: > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > he can catch up with the thread. Which symptoms? I can no longer reproduce the hang-on-close bug. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> "Steven Hartland" <[EMAIL PROTECTED]> writes:
> > Any one got any pointers on this, the machine we running this app on is over
> > 90% idle so I really don't want to have to install a second machine just to
> > workaround a limit on the number of pty's, surely there's a way to increase
> > this?
>
> You need to change the way ptys are named in pty_create_slave() and
> pty_clone() in sys/kern/tty_pty.c. Just changing names won't help as
> the sequence is also hardcoded in pty_clone().
>
> You also need to change grantpt(), openpty() and any other userland code
> which has hardcoded knowledge of the naming scheme:
>
> [EMAIL PROTECTED] ~% gfs pqrsPQRS
> src/sys/kern/tty_pty.c: static char *names = "pqrsPQRS";
> src/sys/kern/tty_pty.c: * pts ==
> /dev/tty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
> src/sys/kern/tty_pty.c: * ptc ==
> /dev/pty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
> src/contrib/telnet/telnetd/sys_term.c: for (cp = "pqrsPQRS"; *cp; cp++) {
> src/usr.sbin/ac/ac.c: strchr("pqrsPQRS",
> usr.ut_line[3]) != 0 ||
> src/lib/libutil/pty.c: for (cp1 = "pqrsPQRS"; *cp1; cp1++) {
> src/lib/libc/stdlib/grantpt.c: #define PT_DEV1 "pqrsPQRS"
>
> Alternatively, set kern.pts.enable to 1, and find and fix the
> hang-on-close bug in the pts code (if it hasn't been fixed already)
Looks like it hasn't been. A friend who tried to set up an access
server for his company stumbled upon it.
>
> DES
> --
> Dag-Erling Smørgrav - [EMAIL PROTECTED]
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
--
If it's there, and you can see it, it's real.
If it's not there, and you can see it, it's virtual.
If it's there, and you can't see it, it's transparent.
If it's not there, and you can't see it, you erased it.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
On 10/2/07, Vlad GALU <[EMAIL PROTECTED]> wrote: > On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > > Vlad GALU <[EMAIL PROTECTED]> writes: > > > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > > > Alternatively, set kern.pts.enable to 1, and find and fix the > > > > hang-on-close bug in the pts code (if it hasn't been fixed already) > > > Looks like it hasn't been. A friend who tried to set up an access > > > server for his company stumbled upon it. > > > > kib@ says it has as of sys/kern/tty_pts.c rev 1.15 (2007-07-03). Has > > your friend tried with a sufficiently recent kernel? > >I can't tell for sure, he tried a week or two ago, with a recent > snapshot. I forwarded him your mail, I hope he'll retry and get back > to me. > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so he can catch up with the thread. > > > > DES > > -- > > Dag-Erling Smørgrav - [EMAIL PROTECTED] > > > > > -- > If it's there, and you can see it, it's real. > If it's not there, and you can see it, it's virtual. > If it's there, and you can't see it, it's transparent. > If it's not there, and you can't see it, you erased it. > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
"Steven Hartland" <[EMAIL PROTECTED]> writes:
> Any one got any pointers on this, the machine we running this app on is over
> 90% idle so I really don't want to have to install a second machine just to
> workaround a limit on the number of pty's, surely there's a way to increase
> this?
You need to change the way ptys are named in pty_create_slave() and
pty_clone() in sys/kern/tty_pty.c. Just changing names won't help as
the sequence is also hardcoded in pty_clone().
You also need to change grantpt(), openpty() and any other userland code
which has hardcoded knowledge of the naming scheme:
[EMAIL PROTECTED] ~% gfs pqrsPQRS
src/sys/kern/tty_pty.c: static char *names = "pqrsPQRS";
src/sys/kern/tty_pty.c: * pts ==
/dev/tty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
src/sys/kern/tty_pty.c: * ptc ==
/dev/pty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
src/contrib/telnet/telnetd/sys_term.c: for (cp = "pqrsPQRS"; *cp; cp++) {
src/usr.sbin/ac/ac.c: strchr("pqrsPQRS",
usr.ut_line[3]) != 0 ||
src/lib/libutil/pty.c: for (cp1 = "pqrsPQRS"; *cp1; cp1++) {
src/lib/libc/stdlib/grantpt.c: #define PT_DEV1 "pqrsPQRS"
Alternatively, set kern.pts.enable to 1, and find and fix the
hang-on-close bug in the pts code (if it hasn't been fixed already)
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
On 10/2/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > Vlad GALU <[EMAIL PROTECTED]> writes: > > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > > Alternatively, set kern.pts.enable to 1, and find and fix the > > > hang-on-close bug in the pts code (if it hasn't been fixed already) > > Looks like it hasn't been. A friend who tried to set up an access > > server for his company stumbled upon it. > > kib@ says it has as of sys/kern/tty_pts.c rev 1.15 (2007-07-03). Has > your friend tried with a sufficiently recent kernel? I can't tell for sure, he tried a week or two ago, with a recent snapshot. I forwarded him your mail, I hope he'll retry and get back to me. > > DES > -- > Dag-Erling Smørgrav - [EMAIL PROTECTED] > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
On Tue, Oct 02, 2007 at 02:05:03PM +0200, Dag-Erling Smørgrav wrote:
> "Steven Hartland" <[EMAIL PROTECTED]> writes:
> > Any one got any pointers on this, the machine we running this app on is over
> > 90% idle so I really don't want to have to install a second machine just to
> > workaround a limit on the number of pty's, surely there's a way to increase
> > this?
>
> You need to change the way ptys are named in pty_create_slave() and
> pty_clone() in sys/kern/tty_pty.c. Just changing names won't help as
> the sequence is also hardcoded in pty_clone().
>
> You also need to change grantpt(), openpty() and any other userland code
> which has hardcoded knowledge of the naming scheme:
>
> [EMAIL PROTECTED] ~% gfs pqrsPQRS
> src/sys/kern/tty_pty.c: static char *names = "pqrsPQRS";
> src/sys/kern/tty_pty.c: * pts ==
> /dev/tty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
> src/sys/kern/tty_pty.c: * ptc ==
> /dev/pty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv]
> src/contrib/telnet/telnetd/sys_term.c: for (cp = "pqrsPQRS"; *cp; cp++) {
> src/usr.sbin/ac/ac.c: strchr("pqrsPQRS",
> usr.ut_line[3]) != 0 ||
> src/lib/libutil/pty.c: for (cp1 = "pqrsPQRS"; *cp1; cp1++) {
> src/lib/libc/stdlib/grantpt.c: #define PT_DEV1 "pqrsPQRS"
>
> Alternatively, set kern.pts.enable to 1, and find and fix the
> hang-on-close bug in the pts code (if it hasn't been fixed already)
This last option is only available if you are running 7-CURRENT though.
The pts code is not in 6-STABLE (or older.)
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
Vlad GALU <[EMAIL PROTECTED]> writes: > Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes: > > Alternatively, set kern.pts.enable to 1, and find and fix the > > hang-on-close bug in the pts code (if it hasn't been fixed already) > Looks like it hasn't been. A friend who tried to set up an access > server for his company stumbled upon it. kib@ says it has as of sys/kern/tty_pts.c rev 1.15 (2007-07-03). Has your friend tried with a sufficiently recent kernel? DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to enable more than 256 pty's?
Any one got any pointers on this, the machine we running this app on is over 90% idle so I really don't want to have to install a second machine just to workaround a limit on the number of pty's, surely there's a way to increase this? Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
