I seem to be getting different behavior depending on how I start my
application, either by launching a pterm then starting the app, or by
putting the following in a script (which is what I want to do, I want
the app to start automatically when the computer is turned on):
or pterm or pterm -G
The difference in behavior has to do with receiving signals - I send a
SIGUSR2 to all the processes in my app to force an orderly shutdown. If
I start the app manually from a pterm it works, if I launch the app from
a script several processes do not seem to receive the signal and cannot
be killed. pidin says they are reply blocked on io-net, which makes no
sense to me (only one of them interacts with the network). Anyway, what
I want to do is start the app from a script I have also tried:
pterm -l -G
This starts a shell but does not start the program. If I then manually
start the program everything works correctly(?!?). So how can I get the
above statement to start the program? It seems like that would solve my
problem. Or is there a way to tell the pterm (from a script)once it is
started to run a program?
I seem to be getting different behavior depending on how I start my
application, either by launching a pterm then starting the app, or by
putting the following in a script (which is what I want to do, I want
the app to start automatically when the computer is turned on):
name of program> or pterm or pterm -G <name of
program
The difference in behavior has to do with receiving signals - I send a
SIGUSR2 to all the processes in my app to force an orderly shutdown. If
I start the app manually from a pterm it works, if I launch the app from
a script several processes do not seem to receive the signal and cannot
be killed. pidin says they are reply blocked on io-net, which makes no
sense to me (only one of them interacts with the network). Anyway, what
I want to do is start the app from a script I have also tried:
pterm -l -G <name of program
This starts a shell but does not start the program. If I then manually
start the program everything works correctly(?!?). So how can I get the
above statement to start the program? It seems like that would solve my
problem. Or is there a way to tell the pterm (from a script)once it is
started to run a program?
I am trying to start a c program. And as I stated in the original post,
the problem is not starting the program, but that the environment (using
the term loosely, I can’t actually find a difference in the environment)
in which it runs is different depending on whether I type the name of
the program in a shell (works correctly) or start it from the script
/root/.ph/phapps (does not work correctly, specifically in regards to
receiving signals).
Also, the syntax you mention (pterm sh doesn’t seem to
work. I don’t think sh is a valid argument for pterm.
WeN wrote:
r u tryin to start a c program or a script from pterm?
To start a script from pterm, you need to do this 'pterm sh '.
Otherwise, it should work.
Bruce Davis <> bruce.r.davis@boeing.com> > wrote in message
news:> 3B2A5019.EA5D8A91@boeing.com> …
I seem to be getting different behavior depending on how I start my
application, either by launching a pterm then starting the app, or by
putting the following in a script (which is what I want to do, I want
the app to start automatically when the computer is turned on):
name of program> or pterm or pterm -G <name of
program
The difference in behavior has to do with receiving signals - I send a
SIGUSR2 to all the processes in my app to force an orderly shutdown. If
I start the app manually from a pterm it works, if I launch the app from
a script several processes do not seem to receive the signal and cannot
be killed. pidin says they are reply blocked on io-net, which makes no
sense to me (only one of them interacts with the network). Anyway, what
I want to do is start the app from a script I have also tried:
pterm -l -G <name of program
This starts a shell but does not start the program. If I then manually
start the program everything works correctly(?!?). So how can I get the
above statement to start the program? It seems like that would solve my
problem. Or is there a way to tell the pterm (from a script)once it is
started to run a program?