Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 323
  • Last Modified:

Problem calling exec after program has been started using rexec

OS Solaris 2.8.
Language C/C++
Lets say I have an executable xxx which perfoms certain things like forking a child, which becomes a demon. After that, demon forks another child, which becomes group leader( of new group ) and after that it tries to call 'execvp' to start another executable( aaa ).
Everything works perfectly.

Problem arises when I start xxx from another program using 'rexec'.
While debugging xxx, it behaves correctly till the call execvp happens.
Here is what I see in workshop:
dbx: process 6733 about to exec("/export/home/izh1/its/bin/aaa")
dbx: warning: LO "/export/home/izh1/its/src/-" destroyed while there are references to it
Reading aaa

>>loading
>>reading additional symbolic information

execution completed, exit code is 795441768
(dbx)

Now I will show you successfull case.
In case I am starting xxx from command line than in the same place (in workshop) I would get:
dbx: process 6733 about to exec("/export/home/izh1/its/bin/aaa")
dbx: warning: LO "/export/home/izh1/its/src/-" destroyed while there are references to it
Reading aaa
Reading libbla1.so
Reading libbla2.so
Reading libbla3.so
(dbx)
And worshop ends up in the aaa process.

Can anyone help me out to understand what is the problem?  Why program which works perfectly stops working properly after it has been started using rexec?
Any inputs are appreciated.

0
igor1026
Asked:
igor1026
1 Solution
 
OtetelisanuCommented:
If you start with rexec must
the environemet variable in the
script same as to the rserver.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now