Yes, I'll give that a try and update this post
Main Topics
Browse All TopicsI have a strange problem with an application, whereby it appears that it hangs up after around 30 minutes of being started
This happens on some systems but not on others
It seems that there is a hangup delay which is determined by the TMOUT variable within the bourne shell, root account which is set to 1800
However, this variable is set on both the systems that have this problem as well as those that don't
I have compared the following details between systems with the problem and those without:
- I've checked all the environment variables using the set command (not env) and I can't see any differences between the systems
- I have checked the sshd configuration on the servers and they are the same
- I have checked the application startup script and binary which it calls and they are the same
- Same hardware, software and versions
- Running the commands with 'nohup' does not resolve the issue on the affected systems
Has anyone experienced a similar problem?
The systems running Solaris 10 Generic_118833-36 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T200
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
A little clarification on the issue
What happens is that an administrator logs into the system, starts the process from the default bourne shell and then logs out. This then causes the process to 'hangup'
It happens on some systems but not on others i.e. on some systems the process keeps running after the administrator has logged out
It causes an issue on production systems as, although, we know it won't happen if somestarts the process from a Bash shell, any procedure that relies on this is prone to human error i.e. an operator may forget to run a bash then start the process...
As far as I can see the builds of the systems are the same, but there may be some subtle differences
It seems to me that Bash is sending different signals than Bourne. However, I need to concentrate on the Bourne shell as this is the default
Does anyone know of a command I can run to identify the version of the Bourne shell or any other check I can run to highlight differences between the systems before looking into signals and truss?
Thanks
I've have replicated the problem on a test systems and I also ran a perl script to catch signals, although it doens't seem to show much
To replicated the problem, I did the following:
- Logged into system via SSH
- Used 'su' to change the application user
- Start the application
- From another SSH session I ran the perl script in the background and started truss
- Exited the applicated user from it's shell
- Exited the SSH session
Apologies for this post. I had this issue handed to me on the understanding that 'nohup' had been ineffective in resolving the issue. I've found a test systems that did experience the issue (most didn't) and tried running the script with nohup and it worked
Thanks for all help and apologies again for any wasted effort
Business Accounts
Answer for Membership
by: liddlerPosted on 2009-09-16 at 08:32:12ID: 25346717
can you use the truss command to see what the application is doing?
Start your process and record PID
use script to start loggin
script /tmp/out
truss -p <PID>
when the process hangs, exit script session and then review the truss output file (/tmp/out) to see what it was doing when it hung and see if you can see any errors at that point it time