HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- /bin/sh scripts: process still alive when the fath...
Operating System - HP-UX
1833495
Members
2646
Online
110052
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2003 12:09 AM
09-18-2003 12:09 AM
I'd like to know if it is possible that a script 'X' (which contains a loop with a sleep) launched from another script 'Y', remains alive when the script 'Y' die ?
1. I think I have to use the trap instruction, but I don't know exactly how.
2. Could be another solution ?
I hope I'm clear enough !
1. I think I have to use the trap instruction, but I don't know exactly how.
2. Could be another solution ?
I hope I'm clear enough !
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2003 12:16 AM
09-18-2003 12:16 AM
Solution
Two things I can think of here.
Probably the most sensible thing is to run script X using the "nohup" command.
If you want to trap signals in a script, choose your signal "kill -l" will list the possible signals and do a
trap "" 2 for example.
I think SIGQUIT is the one you are after but signals get sent to all processes in a process group so you would have to trap pretty much everything for all the possible signals that might have killed the parent.
Probably the most sensible thing is to run script X using the "nohup" command.
If you want to trap signals in a script, choose your signal "kill -l" will list the possible signals and do a
trap "" 2 for example.
I think SIGQUIT is the one you are after but signals get sent to all processes in a process group so you would have to trap pretty much everything for all the possible signals that might have killed the parent.
Never preceed any demonstration with anything more predictive than "watch this"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2003 01:38 AM
09-18-2003 01:38 AM
Re: /bin/sh scripts: process still alive when the father die.
Thanks really a lot. It works fine with the 'nohup' instruction.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP