I am limited to 24 tty qnx4 sessions. When I try to start the 25th session I
got an error message: cannot start program ‘/bin/sh’
This is my sysinit file:
Dev.pty -n16 &
Dev.pty -n16 -lq &
Dev.pty -n16 -lr &
This is what I can see in my /dev folder:
ptyp0, ptyp1, …, ptypf
ptyq0, ptyq1, …, ptyqf
ptyr0, ptyr1, …, ptyrf
ttyp0, ttyp1, …, ttypf
ttyq0, ttyq1, …, ttyqf
ttyr0, ttyr1, …, ttyrf
Normally, I should have 16*3=48 sessions. Unfortunately, I have only 24
sessions.
If I try to start a new “Dev.pty -n16 -ls &”, I still have only 24 sessions.
Does someone know what I forgot to have 48 qnx4 tty sessions?
Louis Francoeur <lfrancoeur@silbec.com> wrote:
I am limited to 24 tty qnx4 sessions. When I try to start the 25th session I
got an error message: cannot start program ‘/bin/sh’
Hm… I run with:
Dev -n 120
Dev.pty -n16
Dev.pty -lq -n16
And was able to open pterms all the way up to ttqe, which would be
16 + 15 = 31.
Now… are you sure it is a pty error? What are you doing to try and
test that the 25th session works?
When I run my 33rd pterm, I get the message printed:
Cannot find a free pseudo tty
Which is quite a different error.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
“David Gibbs” <dagibbs@qnx.com> a écrit dans le message de
news:ctb34n$9sv$1@inn.qnx.com…
Louis Francoeur <> lfrancoeur@silbec.com> > wrote:
I am limited to 24 tty qnx4 sessions. When I try to start the 25th
session I
got an error message: cannot start program ‘/bin/sh’
Hm… I run with:
Dev -n 120
Dev.pty -n16
Dev.pty -lq -n16
And was able to open pterms all the way up to ttqe, which would be
16 + 15 = 31.
Now… are you sure it is a pty error? What are you doing to try and
test that the 25th session works?
When I run my 33rd pterm, I get the message printed:
Cannot find a free pseudo tty
Which is quite a different error.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Perhaps it isn’t a pterm problem, I don’t really know.
What is the limit number of devices with -n parameter on Dev?
if I use: Dev -n 300 &, is it too high?
Louis Francoeur <lfrancoeur@silbec.com> wrote:
Perhaps it isn’t a pterm problem, I don’t really know.
What is the limit number of devices with -n parameter on Dev?
if I use: Dev -n 300 &, is it too high?
If it were a -n issue for Dev, the failure would have appeared when
you tried to run Dev.pty – since you’ve got all the devices in /dev,
you have a large enough Dev.pty setting.
I am limited to 24 tty qnx4 sessions. When I try to start the 25th session I
got an error message: cannot start program ‘/bin/sh’
Again, what are you executing that reports this error – when do you
see this error?
What makes you think this error is related to pseudo ttys?
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Again, what are you executing that reports this error – when do you
see this error?
We have a QNX4 (latest patches) PC with Photon (latest patches) with TCP/IP
package.
Also we have a Windows XP PC with Phindows that access the QNX4 PC.
When I start Pterm sessions from Phindows, everything is fine but when I
reach about 25 pterm sessions I get this message:
cannot start program ‘/bin/sh’
If I try to start 24 telnet sessions (DOS environnement), the 25th session
give me this error:
telnetd: /bin/termdef: Operation not permitted
If I try a mix of telnet sessions and Phindows session, I get error message
when I reach 25th session if (x telnet) + (x Phindows) > 24 sessions.
When I open a pterm in Phindows, the heading screen is like this:
ttyp1: ksh
If I open another pterm
ttyp2: ksh
I could reach this without problem:
ttyq9: ksh
After that I got this:
(close): idle
cannot start program ‘/bin/sh’
Sometimes I can reach ttyqb but I never exceeded it. I don’t know why
sometimes I reach ttyq9 and other times I reach ttyqb.
I do not expect a Photon problem because telnet session do not use Photon I
believe.
“Louis Francoeur” <lfrancoeur@silbec.com> wrote in message
news:ctbd7o$hqn$1@inn.qnx.com…
Again, what are you executing that reports this error – when do you
see this error?
We have a QNX4 (latest patches) PC with Photon (latest patches) with
TCP/IP
package.
Also we have a Windows XP PC with Phindows that access the QNX4 PC.
When I start Pterm sessions from Phindows, everything is fine but when I
reach about 25 pterm sessions I get this message:
cannot start program ‘/bin/sh’
This means that pterm has found a free pseudo-tty but can’t spawn the shell
on it. Perhaps you’re running out of , um, sessions (I know, you’ve been
mentioning sessions all the time…)? Does your buildfile pass a -s option
to Proc? How many sessions does “sin se” list?
Does “pterm -L” fail, too?
I do not expect a Photon problem because telnet session do not use Photon
I
believe.
No, but telnet, just like pterm, uses a pseudo-tty and a creates a new
session.
Wojtek Lerch <Wojtek_L@yahoo.ca> wrote:
“Louis Francoeur” <> lfrancoeur@silbec.com> > wrote in message
news:ctbd7o$hqn$> 1@inn.qnx.com> …
Again, what are you executing that reports this error – when do you
see this error?
We have a QNX4 (latest patches) PC with Photon (latest patches) with
TCP/IP
package.
Also we have a Windows XP PC with Phindows that access the QNX4 PC.
When I start Pterm sessions from Phindows, everything is fine but when I
reach about 25 pterm sessions I get this message:
cannot start program ‘/bin/sh’
This means that pterm has found a free pseudo-tty but can’t spawn the shell
on it. Perhaps you’re running out of , um, sessions (I know, you’ve been
mentioning sessions all the time…)? Does your buildfile pass a -s option
to Proc? How many sessions does “sin se” list?
Or perhaps you are running out of file descriptors? the old “Too many open files”
problem? Try logging in on a console after you’ve used up all your ttys…
Cheers,
-RK
–
[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~museum/
Does your buildfile pass a -s option
to Proc? How many sessions does “sin se” list?
No, my buildfile is like this:
/boot/sys/Proc32
$ /boot/sys/Proc32 -l 1
When I get the error message, “sin se” lists 64 sessions (0 to 63).
Does “pterm -L” fail, too?
No! pterm -L works well when all 64 sessions are open.
What should I do? I don’t know what is “pterm -L”
Thank you
So the question is simple:
How can I have more than 64 sessions in QNX4 ?
Thank you.
I think I have the solution:
Proc32
-s num_sessions
The maximum number of sessions that will be supported (default is 64).
I will change my buildfile like this:
/boot/sys/Proc32
$ /boot/sys/Proc32 -l 1 -s 128
I will have 128 sessions.
Is that correct?
Louis Francoeur wrote:
Does your buildfile pass a -s option
to Proc? How many sessions does “sin se” list?
No, my buildfile is like this:
/boot/sys/Proc32
$ /boot/sys/Proc32 -l 1
When I get the error message, “sin se” lists 64 sessions (0 to 63).
By default, 64 is the max number of sessions that Proc allows. You will
need to add an -s option to Proc to your build file and build a new boot
image.
Does “pterm -L” fail, too?
No! pterm -L works well when all 64 sessions are open.
What should I do? I don’t know what is “pterm -L”
$ use pterm |grep – -L
-L Don’t create new session
Thank you very much Mr. Lerch and Mr. Gibbs.
The case is now closed.
“Wojtek Lerch” <Wojtek_L@yahoo.ca> a écrit dans le message de
news:ctbj3i$7ok$1@inn.qnx.com…
Louis Francoeur wrote:
Does your buildfile pass a -s option
to Proc? How many sessions does “sin se” list?
No, my buildfile is like this:
/boot/sys/Proc32
$ /boot/sys/Proc32 -l 1
When I get the error message, “sin se” lists 64 sessions (0 to 63).
By default, 64 is the max number of sessions that Proc allows. You will
need to add an -s option to Proc to your build file and build a new boot
image.
Does “pterm -L” fail, too?
No! pterm -L works well when all 64 sessions are open.
What should I do? I don’t know what is “pterm -L”
$ use pterm |grep – -L
-L Don’t create new session
Louis Francoeur <lfrancoeur@silbec.com> wrote:
I think I have the solution:
Proc32
-s num_sessions
The maximum number of sessions that will be supported (default is 64).
I will change my buildfile like this:
/boot/sys/Proc32
$ /boot/sys/Proc32 -l 1 -s 128
I will have 128 sessions.
Is that correct?
Yes.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com