bootsys.1m (2012 03)

b
bootsys(1M) bootsys(1M)
-s grace
Causes bootsys to use shutdown with the specified grace period (in seconds). Normally
bootsys uses the reboot -q command and reboots the system immediately with no warn-
ing to users.
-S Directs bootsys to use ssh based protocols instead of
remsh based protocols when com-
municating with remote systems. For more information, see the section
Using SSH with
bootsys.
-t install_tftp_server
Specifies the default system to be used as the Ignite-UX install server. The install_tftp_server
is normally the same system that is being used as the boot server, which is normally the same
as the system on which
bootsys is run. install_tftp_server is a system that has the Ignite-
UX product loaded and is configured with tftp (1) access to the files listed under
FILES.
-g gateway
Specifies the default IP address for the gateway system through which the client system may
reach the install_tftp_server and the SD_server system. (See route (1M)).
If no default gateway is specified, the default is the same as the client host’s IP address and
wild-card routing is performed (on networks that support it).
-m netmask
Specifies the default netmask for the client system to use in reaching the install and SD server
systems. This is necessary if your network uses subnetworks. The netmask is the same as
what is supplied to the ifconfig command (see ifconfig(1M)). netmask may be supplied either in
dot notation (for example, 255.255.248.0) or as a hexadecimal number with a leading 0x (such
as, 0xfffff80).
client
client :IP_address
Specifies the host name(s) of the clients to be rebooted using Ignite-UX. If the client should
use a different IP address when rebooted, or if the client’s IP address cannot be obtained using
nslookup, then it can be specified using the second syntax shown.
-c Ignite-UX_Server
Directs bootsys to execute in "client" or "local" mode. Thus, instead of operating remotely
on one or more clients, bootsys contacts the specified Ignite-UX_Server, and then performs
a local reboot. All other options are processed normally.
-? Display the help screen.
Blocking bootsys Attempts
For computing environments in which the server has
.rhosts permission to all systems, it is sometimes
desirable to block the bootsys command from being able to execute on critical systems. This helps to
prevent users from accidentally targeting the wrong system or a system that is actively in use and not yet
ready to be installed.
bootsys may be blocked by creating the file /.bootsys_block on the clients that you do not want to
be reinstalled. This file may either be empty, contain the word confirm, and/or it may contain a mes-
sage that explains why the client is blocking bootsys. If the file is empty, bootsys refuses to execute
on the target. If the first line of the file contains the word confirm, the user running bootsys on the
Ignite-UX server is asked if client installation should continue. If the file contains any other text, that
text is displayed to the console when the bootsys command was executed. Typically this text is used to
explain why the client is blocking any bootsys attempts.
International Code Set Support
Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many
of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying
environment variables. Help text and some command output not parsed by Ignite-UX will be left in the
user’s specified locale.
Using SSH with bootsys
The
bootsys command remotely executes a series of commands on the client system from the Ignite-UX
server, some of which are protected from waiting for an indefinite period of time. For these reasons,
bootsys must use an access method that does not require the user to repeatedly enter the client
system’s root password. In remsh mode, this is accomplished using the .rhosts file. In SSH mode,
HP-UX 11i Version 3: March 2012 − 3 − Hewlett-Packard Company 3