NAME
grpc_initialize - Initializes Ninf-G.
SYNOPSIS
grpc_error_t grpc_initialize(char *config_file_name)
ARGUMENTS
char *config_file_name- The configuration file for the client
DESCRIPTION
The grpc_initialize() function initializes Ninf-G and the Globus Toolkit used by Ninf-G.
The configuration file specified by config_file_name is read and the values are saved in global
variables within Ninf-G.
If NULL or an empty string is specified in config_file_name , the configuration file specified by the
NG_CONFIG_FILE environment variable is used as the configuration file.
If the NG_CONFIG_FILE environment variable is also undefined or
an empty string, then $HOME/.ngconf is used as the configuration file.
Signal
Ninf-G Client uses SIGINT and SIGTERM. When a Ninf-G Client catches
either SIGINT or SIGTERM, it cancels all outstanding sessions,
destructs all function/object handles, then exits.
Attention
Ninf-G Client may not run normally, on following cases.
-
Setting the signal handler between grpc_initialize() and
grpc_finalize().
For pthread flavor only:
- Creating thread before calling grpc_initialize().
- Removing SIGINT or SIGTERM form signal mask in each threads.
Users' signal handling
If a user intends to use signal handler for SIGINT or SIGTERM,
the user must set the signal handler before calling grpc_initialize().
Ninf-G is able to call the registered signal handler after calling
grpc_initialize().
Attention
For pthread flavor, a signal handler registered by a user is called
from another a thread for signal handling. It is unsafe to call
Pthread APIs from the signal handler.
This function is MT-unsafe.
RETURN VALUE
If successful, GRPC_NO_ERROR is returned. In the case of an error,
Error code is returned.
ERRORS
GRPC_CONFIGFILE_NOT_FOUND- The configuration file does not exist.
- The configuration file could not be read.
GRPC_CONFIGFILE_ERROR- The content of the configuration file is invalid.
GRPC_OTHER_ERROR_CODE- Internal error detected.
last update : $Date: 2005/07/11 07:11:24 $