- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Startup script
HPE 9000 and HPE e3000 Servers
1747999
Members
4579
Online
108756
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
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
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
10-16-2003 06:36 AM
10-16-2003 06:36 AM
Right now i have a script that run under root and starts when the server startup, but it's in cront for root.
Is there other place that i can put it? at this momment, i just kill it, but i don't need this script run anymore.
Thanks
Is there other place that i can put it? at this momment, i just kill it, but i don't need this script run anymore.
Thanks
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2003 05:39 PM
10-16-2003 05:39 PM
Solution
Startup scripts generally go in /sbin/init.d, they have a "case" statement in them, usually with a "start" and "stop" option. Have a look at one of the existing ones in /sbin/init.d and you'll see what I mean. Then, make a symbolic link from your script to /sbin/rcX.d where X is the run level you want the script to run in (probably 3). If you look in /sbin/rc3.d you will see how it works. The S or K at the start of the name indicates Start and Kill respectively and the numbers indicate which order the scripts will be run in during that run level. S links will be run during startup and K scripts will be run at shutdown.
cron isn't really the place to put these scripts. To remove your script from cron go "crontab -e", as root, and delete the offending line (it's vi) and then save the result (it's still vi)
cron isn't really the place to put these scripts. To remove your script from cron go "crontab -e", as root, and delete the offending line (it's vi) and then save the result (it's still vi)
Never preceed any demonstration with anything more predictive than "watch this"
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP