Home > Veritas Storage Foundation™ Volume Manager Manual Pages
VXSVC (1M) |
|
Maintenance Commands |
Table of contents
vxsvc - starts or shuts down the Domain or Local Controller daemon, vxsvc, and also gets the status or version of vxsvc.
vxsvc [-k | -m | -v] | [-r registryFile] [-n] [-f] | -g]
vxsvc
initializes the Domain or Local Controller, loads all registered providers, and listens to connections from clients. It maintains the client context, accepts client requests, and sends back responses and callbacks to the clients.
When run on a Veritas Storage Foundation Manager, vxsvc is referred to as the Domain Controller; when run on a standalone host, vxsvc is referred to as the Local Controller or the VxPAL service for the Veritas Enterprise Administrator (VEA Java Console) to connect to and manage the local host.
-
-k
-
Stops
vxsvc. This allows a clean shutdown of the Domain or Local Controller. The
vxsvc -k
call is synchronous and returns when the Domain or Local Controller shuts down successfully. The
vxsvc -k
command shuts down the service only if it is in the
RUNNING
mode. In any of the other states of the service (NOT RUNNING,
START PENDING,
STOP PENDING,
UNKNOWN), the command returns an error saying that the Controller cannot be stopped. Refer to the
-m
option to get more details about the state of the Controller.
-
-g
-
Starts
vxsvc
in such a way that when the
vxsvc --k
command is invoked to stop the Controller, it performs a graceful shutdown of the Controller instead of killing the process. This option enables working with tools like
valgrind
that provide a summary report only if the shutdown is graceful.
-
-m
-
Returns the state of the Domain or Local Controller. It can be one of the following:
RUNNING
- The Controller is up and running.
START PENDING
- The Controller is in the process of starting.
STOP PENDING
- The Controller is in the process of shutting down.
NOT RUNNING
- The Controller is shut down.
UNKNOWN
- The state of the Controller cannot is not known as the process that has fired
vxsvc -k
stopped abruptly without releasing the lock. The process ID can be obtained from the file
/var/vx/isis/vxisis_shutdown.lock. If the process ID is invalid, remove the
/var/vx/isis/vxisis_shutdown.lock
file.
-
-v
-
Prints the version of the Domain or Local Controller.
-
-r registryFile
-
Specifies the registry file to be used. The default file is
/etc/vx/isis/Registry. The Controller picks up provider entries from the registry.
-
-n
-
Specifies that authentication is not required for the client connections. Use this option while testing only.
-
-f
-
Starts
vxsvc
in the foreground. This is useful while debugging
vxsvc. Without this flag,
vxsvc
forks the background daemon process. The foreground process exits when the startup processing for
vxsvc
is complete. It is not advisable to run the Controller in the foreground for production environments.
/etc/vx/isis/Registry
- Default registry file used by
vxsvc.
/var/vx/isis/vxisis.log
- Log file written to by
vxsvc.
Only one Domain or Local Controller daemon can run on a host at a time. You can also use the script
vxsvcctrl
to start, stop, restart, and get version information about
vxsvc. By default,
vxsvc
resides in:
/opt/VRTSob/bin
vxsvcctrl(1m)
Copyright (c) 2007 Symantec Corporation. All rights reserved.
Last updated: 05/17/2007
Copyright ©2009 Symantec Corporation
All rights reserved.