Operating System - HP-UX
1843997 Members
2259 Online
110226 Solutions
New Discussion

PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

 
Enrico Venturi
Super Advisor

PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

Hello colleagues,
I got this error when I try to open the pty ...
I cannot see the problem :-(

I increased the NSTRPTY but it was unuseful...

can anyone help me?

regards
Enrico
5 REPLIES 5
Fabio Ettore
Honored Contributor

Re: PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

Ciao Enrico,

I think you obtain it when you telnet,remsh,rlogin into that system (can you confirm?)

Try
# insf -e

Anyway what is the actual value for

maxusers
npty
nstrpty
nstrtel

?

Best regards,
Ettore
WISH? IMPROVEMENT!
Enrico Venturi
Super Advisor

Re: PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

maxusers=128
nstrpty=200
nstrtel=60
npty=60

I get this error when I run the open_proc procedure ..
It's a PERL library using the PTY to overcome a buffering problem between producer and consumer when using the open3 command.
(see the perldoc perlipc, place the cursor to Unix buffering)

thanks
Enrico
Fabio Ettore
Honored Contributor

Re: PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

I don't know Perl, anyway if 'insf -e' doesn't help you then try

# insf -d pty -n 200

It will increase run-time running pty device files to 200.

If it solves your problem then increase npty to 200 in kernel too by SAM.

Hope this helps you (a little bit more!)

Ciao.
Ettore
WISH? IMPROVEMENT!
Enrico Venturi
Super Advisor

Re: PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

No, it still doesn't work :-(

I think it's matter of access rights or something similar.....

Mike Stroyan
Honored Contributor

Re: PTY: error, could not open slave, /dev/pts/1, errno=Resource temporarily unavailable

You could use the tusc system call tracing tool
to see exactly what calls are made and what
their results are. That could be easier to
interpret than the perl error message.

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/tusc-7.5/