Hi all,
> I've got a question about recent optimizations in lcg-ce (addition of
> globus-gass-cache-marshal and globus-job-manager-marshal) - it has been
> said that configuration files can be found in globus/etc location, but I
> didn't manage to find any documentation about what that configuration
> actually mean or does. [...]
Pasted from https://gus.fzk.de/ws/ticket_info.php?ticket=35835 and slightly
adjusted (it will be put on a Wiki page):
-----------------------------------------------------------------------------
logf <path> - location of the log file (default is relative to
GLOBUS_LOCATION)
maxproc <numeric> - maximum number of parallel requests [this is the most
useful variable for tuning] (5 by default)
tick <numeric> - hung child processes are killed every this number of
seconds (if no other events are happening)
(300 by default).
reqtout <numeric> - client should send a complete request in this number of
seconds after connection (10 by default)
proctout <numeric> - each request (child process) is allowed to run this
number of seconds (600 by default)
reqlimit <numeric> - maximum size of a request in bytes (16384 by default).
One should increase this limit if environment is very
large.
window <numeric> - data block for recv/send in bytes, probably should never
be changed (default value is 4096 (x86 page size)).
debug <numeric> - debug level. There are three of them: 0 - only warnings
(default), 1 - all messages, 2 - stderr is being
redirected to the log file (bad for log parsers, but
good for catching problems in perl jobmanagers)
All parameters (except debug 1 -> 2) could be changed online (modify
config file and send a sighup). Both daemons create pidfiles in /var/run/
but their location is not configurable.
-----------------------------------------------------------------------------
|