egocontrol
Starts EGO on a remote Linux® host in the cluster. Use the egocontrol command to start EGO on Linux hosts only when you do not want the egosh command to run as the root user in your cluster.
Synopsis
- -h
-
When running the egocontrol command in shell console mode, prints command usage to stderr and exits.
- help
-
When running the egocontrol command in console mode, displays usage information.
ego start [-f] [-n commands] [host_name … | all]
Starts EGO on the local host or, if issued from the primary host, starts EGO on all Linux hosts in the cluster.
This is an administrative subcommand. You must be logged on with root permissions to issue this command.
setuid
on the
egocontrol binary and change its owner to root. See egosetsudoers.- -f
- Forces the action on the host without validating the configuration file. Use this option when
you are issuing the command from within a script and do not want the script to stop running to
respond to prompts.
This option is automatically applied if the value for the -n commands option is greater than one.
- -n commands
- Specifies the number of commands to run in parallel. Executing commands in parallel allows the
cluster to start faster. Use forked
processes to implement parallel execution.
There is no hard limit to the number of commands; however, the maximum number of commands is limited by the operating system user limits, and can cause the forking to fail.
If the value for the -n commands option is greater than one, the command automatically applies the -f option.
- host_name …
- Specifies the name of the host or hosts on which to start EGO. To specify multiple hosts,
separate the host names with a space.
You cannot use this option from a compute host unless the primary host is up and running.
To use this option, you must have root permission on each host and have rsh configured for your account for each host. You may need to add an entry for the local host in the .rhosts file for root.
- all
- Starts EGO on all hosts in the cluster. Use this option when you want to start the entire
cluster.
You cannot use this option from a compute host unless the primary host is up and running.
To use this option, you must have root permission on each host and have rsh configured for your account. You may need to add an entry for the local host in the .rhosts file for root.