grpwise (1)

Name

grpwise - GroupWise Script

Syntax

grpwise start [object] 
grpwise status [object] 
grpwise stop [object]
grpwise restart [object]
grpwise restartall 
grpwise print [object]

The objects are:

Admin Service: gwadminservice
POA:           post_office_name.domain_name
MTA:           domain_name
GWIA:          gwia.domain_name
DVA:           gwdva.post_office_name

NOTE:The Monitor Agent is not controlled by the grpwise script. It has its own script named grpwise-ma, which works essentially the same as the grpwise script.

Description

The grpwise script is created during installation and can control any agents installed on the local server. It is created in the /etc/init.d folder. It works in conjunction with the gwha.conf file, which is created in the /etc/opt/novell/groupwise folder. The gwha.conf file lists the agents installed on the local server so that the grpwise script knows which agents to start.

The GroupWise agents are Run Control compliant. During installation, a symbolic link is created from /etc/init.d/grpwise to /usr/sbin/rcgrpwise. Typically, /usr/sbin is already on your path. This enables you to run rcgrpwise from any folder, rather than changing to /etc/init.d in order to run the grpwise script.

Options

Usage Options:

start

Starts all GroupWise agents on the local server or the specific GroupWise agent specified in the grpwise command. A green “done” indicates that an agent is running. If a green “done” does not appear, the agent was unable to start.

status

Displays status for all GroupWise agents on the local server or the specific GroupWise agent specified in the grpwise command. A green “running” indicates that an agent is running. A black “unused” indicates that an agent is not running.

stop

Stops all GroupWise agents on the local server or the specific GroupWise agent specified in the grpwise command. A green “done” indicates that an agent is stopped. A black “unused” indicates that an agent is not running and therefore cannot be stopped.

restart

Restarts all GroupWise agents on the local server or the specific GroupWise agent specified in the grpwise command. A green “done” indicates that an agent is stopped. A black “unused” indicates that an agent is not running and therefore cannot be stopped. The agents then start again with the standard start status indicators.

print

Lists settings for all GroupWise agents in the gwha.conf file or for the GroupWise agent specified in the grpwise command.

post_office_name.domain_name

Specifies the POA to start or stop. The syntax allows for multiple POAs running on the same server and specifies which POA to start or stop.

domain_name

Specifies the MTA to start or stop. The syntax allows for multiple MTAs running on the same server and specifies which MTA to start or stop.

gwia.domain_name

Specifies the GWIA to start or stop. The syntax allows for multiple GWIAs running on the same server and specifies which GWIA to start or stop.

gwdva.post_office_name

Specifies the DVA to start or stop. The syntax allows for multiple DVAs running on the server. Running multiple DVAs on a server is not recommended.

Help Options:

--help , -?

Displays the help information and exits.

Files

/etc/opt/novell/groupwise/gwha.conf

GroupWise High Availability Service (gwha) configuration file. This configuration file lists all information necessary to start and stop each GroupWise agent that is installed on the server. For example, an entry for an MTA might look similar to this:

server    = /opt/novell/groupwise/agents/bin/gwmta
command   = /etc/init.d/grpwise
startup   = /gwsystem/provo1/provo1.mta
delay     = 2
wait      = 10

The server = setting specifies the full path to the agent executable.

The command = setting specifies the full path to the grpwise script.

The startup = setting specifies the name of the agent startup file. Agent startup files are found in the following locations:

/post_office_folder/post_office_name.poa
/domain_folder/domain_name.mta
/domain_folder/wpgate/gwia/gwia.cfg
/post_office_folder/post_office_name.dva

The delay = setting controls the length of time between when the script issues the command to start an agent and when the script displays a message indicating that the agent has started. The default delay time is 2 seconds.

The wait = setting controls the length of time between when the script issues the command to stop an agent and when the script kills the agent if the agent has not yet stopped. The default wait time is 10 seconds.

By default, the grpwise script starts the agents as services with no user interface. If you want a user interface, you can add a show = yes line for each agent that you want to have a user interface. An agent that runs with a user interface cannot be managed in the GroupWise Admin console because it is not running as a service.

Examples

This script must be run as root. If you have configured the GroupWise agents to run as a non-root user, they switch over to that user after they have started.

In all of the examples below, replace /etc/init.d/grpwise with rcgrpwise to run the script from any folder.

/etc/init.d/grpwise start

Starts all GroupWise agents that are installed on the server.

/etc/init.d/grpwise status development.provo1

Shows the status of the Development post office POA. The Development post office belongs to the Provo1 domain.

/etc/init.d/grpwise stop gwia.provo1

Stops the GWIA that belongs to the Provo1 domain.

Diagnostics

If a GroupWise agent fails to start when using the grpwise script, try starting the agent manually, as described in the man page for each agent. You might receive an error message indicating why the agent is failing to start.

If you have changed the non-root user that you want the agent to run by modifying the /etc/opt/novell/groupwise/agents/uid.conf file, you might have forgotten to delete the corresponding uid.run file in the domain or post office folder that the agent services. Delete the uid.run file, then use the grpwise script to try to start the agent again.