01-25-2006
In HP-UX, the directory is /sbin/init.d. This is where your startup script should be. You will find a template script in that directory that you can copy and modify. But as RTM said, there is more to it than that. There is another directory /etc/rc.config.d where you have files that specify whether a service should start during boot or not. Go through a few other startup scripts to see how that works. Lastly create links in the /sbin/rc?.d directory. The links are of the form S??scriptname and K??scriptname and are linked to the startup script in /sbin/init.d directory.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all Unix fans.
What files are involved in the Unix boot sequence,
i guess there is alot of them but some must be the main files?
For example the service SENDMAIL starts on our Unix machine
where should i edit so that it will not start at BOOT.
initd.conf? rc2.d?
I hope you... (6 Replies)
Discussion started by: sajjan2
6 Replies
2. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
I have some problems with my library when the sytem boot :
When HPUX is booting, HPUX and STAPE claim the drive initially. HPUX assigns an instance
number. The instance number is tied to the hardware path. Near the end of the boot, the ATDD driver claims the drive from
STAPE based... (1 Reply)
Discussion started by: delphine
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have two machines, one is a E3500 and the other one is a V490;
I face a strange issue with both of them. The boot up sequence gives the output of the devalias command. Has anybody faced this?? Please do let me know what needs to be done o resolve this.
Regards,
NP (1 Reply)
Discussion started by: nitinp82
1 Replies
5. Linux
I am running linux red hat and I need to know the command to view the boot up process.... (that is the driver initialization, drive mount, etc).... Does anyone know this command? (7 Replies)
Discussion started by: Franco
7 Replies
6. Solaris
Hi all,
I have solaris and xp installed...
Usually solaris occupies the first boot slot.
So i wanted to know if it is possible to change the boot sequence to xp first and then solaris? (5 Replies)
Discussion started by: wrapster
5 Replies
7. Filesystems, Disks and Memory
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
" .....
EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies
8. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
9. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
10. Shell Programming and Scripting
Hi all,
I have a file like this
ID 3BP5L_HUMAN Reviewed; 393 AA.
AC Q7L8J4; Q96FI5; Q9BQH8; Q9C0E3;
DT 05-FEB-2008, integrated into UniProtKB/Swiss-Prot.
DT 05-JUL-2004, sequence version 1.
DT 05-SEP-2012, entry version 71.
FT COILED 59 140 ... (1 Reply)
Discussion started by: manigrover
1 Replies
pdc(1M) pdc(1M)
NAME
pdc - processor-dependent code (firmware)
DESCRIPTION
is the firmware that implements all processor-dependent functionality, including initialization and self-test of the processor. Upon com-
pletion, it loads and transfers control to the initial system loader (isl(1M)). Firmware behavior varies somewhat, depending on the hard-
ware as described below.
To load from an external medium, must know the particular device on which resides. Typically the device is identified by the Primary Boot
Path that is maintained by in Stable Storage. A path specification is an I/O subsystem mnemonic that varies according to hardware model.
When the processor is reset after initialization and self-test complete, reads the Console Path from Stable Storage, and attempts to ini-
tialize the console device. If the initialization fails, attempts to find and initialize a console device. Algorithms used to find a con-
sole device are model-dependent. then announces the Primary Boot, Alternate Boot, and Console Paths.
If (see isl(1M)) is enabled, provides a 10-second delay, during which time the operator can override the sequence by typing any character
on the console. If the operator does not interrupt this process, initializes and reads from the Primary Boot Path. On models that support
autosearch, if this path is not valid and (see isl(1M)) is enabled, then searches to find a bootable medium.
If allowed to complete, a list of potentially bootable devices is displayed, labeled with abbreviated path identifiers (P0, P1, etc). A
simple menu is then displayed where the user can:
o Boot a specific device, using the abbreviated path identifier, or the full mnemonic.
o Start a device search where the contents are searched for IPL images (note the first search only identified devices and did not
check the contents).
o Enter the boot administration level.
o Exit the menu and return to autobooting
o Get help on choices
If the sequence is unsuccessful, overridden by the operator, or not enabled in the first place, interactively prompts the operator for the
Boot Path to use. Any required path components that are not supplied default to zero.
The Primary Boot, Alternate Boot, and Console Paths as well as and enable can be modified via
SEE ALSO
boot(1M), isl(1M).
PA-RISC Systems Only pdc(1M)