My NT IDE use rsh to launch a make on QRTP like that:
rsh serveur_qnx -l build cd my_dir;make
I’ve started inetd -d
Immediately, inetd says:
someone wants shell
accept, ctrl 3
spawn (/usr/sbin/rshd): pid xxxxxxxx
rshd is blocked on SIGWAITINFO.
One coffee later (oups!), one minute later my commands are executed.
Why ??
answer quickly please, I begin to be a little bit nervous! ;o)
Thanks,
Alain.
Hello Alain,
When your use the -d option you are telling it to turn on debugging. If this isn’t what you mean to do, try running it without the -d option.
Regards,
Dave B.
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
My NT IDE use rsh to launch a make on QRTP like that:
rsh serveur_qnx -l build cd my_dir;make
I’ve started inetd -dImmediately, inetd says:
someone wants shell
accept, ctrl 3
spawn (/usr/sbin/rshd): pid xxxxxxxxrshd is blocked on SIGWAITINFO.
One coffee later (oups!), one minute later my commands are executed.
Why ??answer quickly please, I begin to be a little bit nervous! ;o)
Thanks,
Alain.
Applications Mail Group a écrit :
Hello Alain,
When your use the -d option you are telling it to turn on debugging. If this isn’t what you mean to do, try running it without the -d option.
Regards,
Dave B.Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
My NT IDE use rsh to launch a make on QRTP like that:
rsh serveur_qnx -l build cd my_dir;makeI’ve started inetd -d
Immediately, inetd says:
someone wants shell
accept, ctrl 3
spawn (/usr/sbin/rshd): pid xxxxxxxxrshd is blocked on SIGWAITINFO.
One coffee later (oups!), one minute later my commands are executed.
Why ??
answer quickly please, I begin to be a little bit nervous! ;o)
Thanks,
Alain.
It’s what I wanted to do because I wanted to know where the problem came from.
Now, I know that inetd receive immediately the message and immediately creates rshd.
The question is:
Why rshd waits about 1’20" before executing my commands?
Alain.
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
Applications Mail Group a écrit :
Hello Alain,
When your use the -d option you are telling it to turn on debugging. If this isn’t what you mean to do, try running it without the -d option.
Regards,
Dave B.Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
My NT IDE use rsh to launch a make on QRTP like that:
rsh serveur_qnx -l build cd my_dir;makeI’ve started inetd -d
Immediately, inetd says:
someone wants shell
accept, ctrl 3
spawn (/usr/sbin/rshd): pid xxxxxxxxrshd is blocked on SIGWAITINFO.
One coffee later (oups!), one minute later my commands are executed.
Why ??
answer quickly please, I begin to be a little bit nervous! ;o)
Thanks,
Alain.It’s what I wanted to do because I wanted to know where the problem came from.
Now, I know that inetd receive immediately the message and immediately creates rshd.
The question is:
Why rshd waits about 1’20" before executing my commands?
It’s probably doing a “gethostbyaddr()” on the NT’s address. The 1 minute
is about a DNS lookup timeout.
-xtang
Xiaodan Tang a écrit :
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
Applications Mail Group a écrit :Hello Alain,
When your use the -d option you are telling it to turn on debugging. If this isn’t what you mean to do, try running it without the -d option.
Regards,
Dave B.Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
My NT IDE use rsh to launch a make on QRTP like that:
rsh serveur_qnx -l build cd my_dir;makeI’ve started inetd -d
Immediately, inetd says:
someone wants shell
accept, ctrl 3
spawn (/usr/sbin/rshd): pid xxxxxxxxrshd is blocked on SIGWAITINFO.
One coffee later (oups!), one minute later my commands are executed.
Why ??
answer quickly please, I begin to be a little bit nervous! ;o)
Thanks,
Alain.It’s what I wanted to do because I wanted to know where the problem came from.
Now, I know that inetd receive immediately the message and immediately creates rshd.
The question is:
Why rshd waits about 1’20" before executing my commands?It’s probably doing a “gethostbyaddr()” on the NT’s address. The 1 minute
is about a DNS lookup timeout.-xtang
Something like that. In fact, the delay was the same for ‘rsh 172.20.22.55 …’ or ‘rsh serveur_qnx 172.20.22.55 …’ ?!?
Sylvain Bourré (QNX France) asked me to add my NT machine’s name in /etc/hosts.
Now it works fine but what did happen exactly?
Thanks,
Alain.