Problems Starting App remotely

Hi
I am running a custom app on an embedded QNX box.
This box has no keyboard or monitor.
It is connected to an NT box via ethernet.

I am trying to start the custom app from NT, via Telnet or
programmatically through RSH ( preferred), but it doesn’t work.
It runs but then it hangs after a bit, in telnet, if I close telnet the
app goes away too! ;(

I can autostart the app from the .profile in the home dir with the
command './APPNAME >dev/null 2> dev/null ’

It seems to me I should be able to add a ‘&’ the the command and it
should run without the telnet session, but alas it doesn’t!

Any ideas?

Keith

Keith Vasilakes <kvasilak@cyberoptics.com> wrote in
news:3C96561A.427ACB4F@cyberoptics.com:

Hi
I am running a custom app on an embedded QNX box.
This box has no keyboard or monitor.
It is connected to an NT box via ethernet.

I am trying to start the custom app from NT, via Telnet or
programmatically through RSH ( preferred), but it doesn’t work.
It runs but then it hangs after a bit, in telnet, if I close telnet the
app goes away too! ;(

I can autostart the app from the .profile in the home dir with the
command './APPNAME >dev/null 2> dev/null ’

It seems to me I should be able to add a ‘&’ the the command and it
should run without the telnet session, but alas it doesn’t!

Try daemonizing the application to seperate it from the shell session you
started. Either use procmgr_daemon() or do the *NIX fork();setsid();fork()
idea.

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

Adam
Thanks for the reply, but I am more confused now than before.
I’ve been through all of my QNX and Watcom books and I don’t see
procmgr_daemon() anywhere.
I am using 4.25 BTW, which is most likely the problem…

Also I would really like to do this via a script, is that not possible??

Keith

Adam Mallory wrote:

Keith Vasilakes <> kvasilak@cyberoptics.com> > wrote in
news:> 3C96561A.427ACB4F@cyberoptics.com> :

Hi
I am running a custom app on an embedded QNX box.
This box has no keyboard or monitor.
It is connected to an NT box via ethernet.

I am trying to start the custom app from NT, via Telnet or
programmatically through RSH ( preferred), but it doesn’t work.
It runs but then it hangs after a bit, in telnet, if I close telnet the
app goes away too! ;(

I can autostart the app from the .profile in the home dir with the
command './APPNAME >dev/null 2> dev/null ’

It seems to me I should be able to add a ‘&’ the the command and it
should run without the telnet session, but alas it doesn’t!

Try daemonizing the application to seperate it from the shell session you
started. Either use procmgr_daemon() or do the *NIX fork();setsid();fork()
idea.


Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

“Keith Vasilakes” <kvasilak@cyberoptics.com> wrote in message
news:3C97AD8B.FD489794@cyberoptics.com

Adam
Thanks for the reply, but I am more confused now than before.
I’ve been through all of my QNX and Watcom books and I don’t see
procmgr_daemon() anywhere.
I am using 4.25 BTW, which is most likely the problem…

You are in a QNX6 related conference, hence you got a QNX6 answer.

Also I would really like to do this via a script, is that not possible??

Keith

Adam Mallory wrote:

Keith Vasilakes <> kvasilak@cyberoptics.com> > wrote in
news:> 3C96561A.427ACB4F@cyberoptics.com> :

Hi
I am running a custom app on an embedded QNX box.
This box has no keyboard or monitor.
It is connected to an NT box via ethernet.

I am trying to start the custom app from NT, via Telnet or
programmatically through RSH ( preferred), but it doesn’t work.
It runs but then it hangs after a bit, in telnet, if I close telnet
the
app goes away too! ;(

I can autostart the app from the .profile in the home dir with the
command './APPNAME >dev/null 2> dev/null ’

It seems to me I should be able to add a ‘&’ the the command and it
should run without the telnet session, but alas it doesn’t!

Try daemonizing the application to seperate it from the shell session
you
started. Either use procmgr_daemon() or do the *NIX
fork();setsid();fork()
idea.


Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

Oh, well then, I’ll be leaving now! :smiley:


You are in a QNX6 related conference, hence you got a QNX6 answer.

Keith Vasilakes <kvasilak@cyberoptics.com> wrote in
news:3C97AD8B.FD489794@cyberoptics.com:

Adam
Thanks for the reply, but I am more confused now than before.
I’ve been through all of my QNX and Watcom books and I don’t see
procmgr_daemon() anywhere.
I am using 4.25 BTW, which is most likely the problem…

Also I would really like to do this via a script, is that not
possible??

Opps, you forgot to mention that tidbit of info (ie. QNX4). You can still
do the *NIX method of daemonization using fork/setsid/fork, or you could
use the nohup tool, which should stop your process from getting the HUP
signal on shell close.

BTW, you should post QNX4 related questions to the QNX4 group for proper
responses.

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>