01-09-2004
Sorry , i have used "ln -s" not "ls -s", i just wrote it wrong.
Like you said fpmurphy, HP-UX uses 3 digits to set the starting order, so i have used S999 to star in last.
I will create the other link with K100 to kill the process, thats a very good tip. But first of all, i want to get it started.
many thanks to you both.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi guys,
May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro.
Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all
The following error was displayed when a sco server (5.0.5) was booted. What should be done to overcome the problem. Replies appreciated.
Bios 03.0
0130688 KB memory good
01 processor(s) in system
remote console dialing on, please wait
connect fail : modem off
cpu clock... (6 Replies)
Discussion started by: raguramtgr
6 Replies
3. UNIX for Dummies Questions & Answers
Evry time I start up my mavhine ,have to type in unix at
Boot
:
Is there a way unix should bootup automatically?
Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies
4. AIX
Hi i installed ssh of version v 1.21 and my AIX is of 5.3.
I want to start my ssh deamon at the startup
can any one please help me out reg..
Thanks in advance.. (1 Reply)
Discussion started by: kmalla
1 Replies
5. AIX
Issue: AIX server freezes on bootup.
Server AIX ver 4.3.3.0
When the AIX server reboots it negotiates NIS. During startup of NFS, customer gets one or more of the following error messages:
0513-056 Timeout waiting for command response. If you specified a foreign host, see the /etc/inittab file... (1 Reply)
Discussion started by: srzaman1
1 Replies
6. UNIX for Advanced & Expert Users
Is it possible to give multiple runlevel options during boot up.. When the Welcome screen appears, i want to give multiple runlevel options.. So the user can boot into any desired runlevel he wants.. Found this kinda interesting.. Any hints and solutions please? (2 Replies)
Discussion started by: srikumar_cs
2 Replies
7. AIX
Hi,
I've got a recent problem with 2 file systems on an AIX 5.3 server. The fs's are marked to auto mount at startup and do show as being mounted after a a restart however if you cd to the mount point and 'df -g .' it shows the fs hasn't actually mounted.
$ mount |grep SQLT0001.0
... (2 Replies)
Discussion started by: m223464
2 Replies
8. UNIX for Dummies Questions & Answers
What is the boot up sequence in UNIX? (2 Replies)
Discussion started by: karthi_g
2 Replies
9. Linux
Hello all,
I have a script callled 'ABCstartup' setup under /etc/rc.d/init.d
Softlink 'S91ABCstartup' pointing to above script has been created under /etc/rc.d/rc3.d
The script is not being executed when the server restarts.
The script runs successfully via manual execution:... (5 Replies)
Discussion started by: hemangjani
5 Replies
10. SCO
I have a known good external SCSI HD running SCO UNIX OpenServer 5.0.7. I decided that I wanted to be able to run this drive on another computer, so I bought the same SCSI card as before (LSI) and then attempted to boot on the other system. The bootup process hung with the error F painit. I've... (13 Replies)
Discussion started by: Transpower
13 Replies
HBOOT(1) LAM TOOLS HBOOT(1)
NAME
hboot - Start LAM on the local node.
SYNOPSIS
hboot [-dhstvNV] [-c conf] [-I inet_topo] [-R rtr_topo]
OPTIONS
-d Turn on debugging. This implies -v.
-h Print the command help menu.
-s Close stdio of child processes.
-t Terminate (tkill(1)) any previous LAM session before starting.
-v Be verbose.
-N Go through the motions but do not actually take any action.
-V Format and print the process schema.
-c conf Use conf as the process schema.
-I inet_topo Set the $inet_topo variable in the process schema.
-R rtr_topo Set the $rtr_topo variable in the process schema.
DESCRIPTION
Most MPI users will probably not need to use the hboot command; see lamboot(1).
The hboot tool can be understood as a generic utility that starts multiple processes on the local node, based on information in a process
schema. It is not restricted to starting LAM. It is part of the startup sequence preformed by lamboot(1).
A process schema is a description of the processes which constitute the operating system on a given node. Naturally, the process schema
used by hboot should be the one that describes LAM on a node. The grammar of the process schema is described in conf(5).
When starting LAM on a remote machine using rsh(1), the open file descriptors of the processes started by hboot must be closed in order for
rsh(1) to exit. This is done by using the -s option. The -t option can be used to force a tkill(1) on the machine before attempting to
start LAM. This feature is used by lamboot(1) to handle the case where a user might start a machine a second time without using lamwipe(1)
to terminate the previous LAM session.
The -I and -R options set their respective variables to the given values. The $inet_topo variable is typically used by the LAM Internet
datalinks that communicate with other nodes. The $rtr_topo variable is passed to the LAM router that handles network and topology informa-
tion. The variables can also be set in the process schema file (see conf(5)) but their values are overridden by the command line options.
When LAM is started, the kernel records all processes that attach to it, including all the processes in the process schema. It is the job
of tkill(1) to use this information to remove these processes from the node.
EXAMPLES
hboot -v
Start LAM on the local node with the default process schema. Report about every step as it is done.
hboot -c myconfig
Boot the local node with the custom process schema, myconfig.
FILES
laminstalldir/etc/lam-conf.lamd
default node process schema, where "laminstalldir" is the directory where LAM/MPI was installed
laminstalldir/etc/lam7.1.4helpfile
Default location for help file for diagnostic messages that hboot may generate.
/tmp/lam-$USER@hostname kill file for the LAM session on machine hostname, where $USER is the userid.
DIAGNOSTICS
Using ps(1) after hboot will display, among others, the LAM processes that have been started. They may be killed one by one with kill(1),
or all at once by killing the LAM kernel process with a HUP signal. The preferred method is to use the LAM tool tkill(1) which should kill
them all at once, and also remove the kill file. New users should make liberal use of ps(1) to gain confidence that the system is working
properly. In a disaster, ps(1) and kill(1) are your only hope of recovery.
SEE ALSO
lamboot(1), tkill(1), conf(5), lam-helpfile(5)
LAM 7.1.4 July, 2007 HBOOT(1)