HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Question regarding /etc/inittab
Operating System - HP-UX
1832552
Members
6133
Online
110043
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
01-23-2008 05:07 PM
01-23-2008 05:07 PM
Hello all.
I have a fairly basic HP-UX start up question that I'd like to confirm with the experts out there.
After the init process is started it reads the /etc/inittab configuration file from top to bottom, correct?
Assuming this is correct, would the /sbin/rc script (and all scripts in sequencer directories /sbin/rc0.d, /sbin/rc1.d, /sbin/rc2.d...) be executed before the "h1" entry if my /etc/inittab file contained the following:
sqnc::wait:/sbin/rc /dev/console 2>&1 # system init
#powf::powerwait:/sbin/powerfail >/dev/console 2>&1 # powerfail
cons:123456:respawn:/usr/sbin/getty console console # system console
#ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600
#ttp2:234:respawn:/usr/sbin/getty -h tty0p2 9600
#ttp3:234:respawn:/usr/sbin/getty -h tty0p3 9600
#ttp4:234:respawn:/usr/sbin/getty -h tty0p4 9600
#ttp5:234:respawn:/usr/sbin/getty -h tty0p5 9600
krsd:123456:respawn:/sbin/krsd -i
sfd:123456:respawn:/sbin/sfd
#ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf
#samd:23456:respawn:/usr/sam/lbin/samd # system mgmt daemon
cim1:3456:respawn:/opt/wbem/sbin/cimserverd
h1:3:respawn:/sbin/init.d/init.cssd run >/dev/null 2>&1
The way I understand it, init would start /sbin/rc and wait for it to complete before proceeding to the next entry in /etc/inittab.
I'm just looking for some clarification on whether an entry such as /sbin/rc3.d/S990oracle would be kicked off before the "h1" entry from the above sample /etc/inittab file.
I hope this question makes sense.
Any feedback is welcomed.
Thank you.
Tom Wolf
I have a fairly basic HP-UX start up question that I'd like to confirm with the experts out there.
After the init process is started it reads the /etc/inittab configuration file from top to bottom, correct?
Assuming this is correct, would the /sbin/rc script (and all scripts in sequencer directories /sbin/rc0.d, /sbin/rc1.d, /sbin/rc2.d...) be executed before the "h1" entry if my /etc/inittab file contained the following:
sqnc::wait:/sbin/rc /dev/console 2>&1 # system init
#powf::powerwait:/sbin/powerfail >/dev/console 2>&1 # powerfail
cons:123456:respawn:/usr/sbin/getty console console # system console
#ttp1:234:respawn:/usr/sbin/getty -h tty0p1 9600
#ttp2:234:respawn:/usr/sbin/getty -h tty0p2 9600
#ttp3:234:respawn:/usr/sbin/getty -h tty0p3 9600
#ttp4:234:respawn:/usr/sbin/getty -h tty0p4 9600
#ttp5:234:respawn:/usr/sbin/getty -h tty0p5 9600
krsd:123456:respawn:/sbin/krsd -i
sfd:123456:respawn:/sbin/sfd
#ups::respawn:rtprio 0 /usr/lbin/ups_mond -f /etc/ups_conf
#samd:23456:respawn:/usr/sam/lbin/samd # system mgmt daemon
cim1:3456:respawn:/opt/wbem/sbin/cimserverd
h1:3:respawn:/sbin/init.d/init.cssd run >/dev/null 2>&1
The way I understand it, init would start /sbin/rc and wait for it to complete before proceeding to the next entry in /etc/inittab.
I'm just looking for some clarification on whether an entry such as /sbin/rc3.d/S990oracle would be kicked off before the "h1" entry from the above sample /etc/inittab file.
I hope this question makes sense.
Any feedback is welcomed.
Thank you.
Tom Wolf
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2008 06:33 AM
01-24-2008 06:33 AM
Solution
Tom,
The rc sequence runs to completion before the next inittab line is processed. So you should be safe with your cssd startup.
I actually verified with a freshly rebooted system and you can do the same.
I checked the /etc/rc.log and the startup time was 9:17:56 and the completion time was 9:19:17.
Then I used "ps -ef |more" and checked the STIME (start up time) for samd and krsd and both were 9:19:17.
This clearly shows that the subsequent statements in inittab are executed after the rc sequence is completed.
The rc sequence runs to completion before the next inittab line is processed. So you should be safe with your cssd startup.
I actually verified with a freshly rebooted system and you can do the same.
I checked the /etc/rc.log and the startup time was 9:17:56 and the completion time was 9:19:17.
Then I used "ps -ef |more" and checked the STIME (start up time) for samd and krsd and both were 9:19:17.
This clearly shows that the subsequent statements in inittab are executed after the rc sequence is completed.
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