Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation about config files is confusing #138

Open
fnevgeny opened this issue Oct 28, 2020 · 0 comments
Open

Documentation about config files is confusing #138

fnevgeny opened this issue Oct 28, 2020 · 0 comments

Comments

@fnevgeny
Copy link

Hello,

The docs (e.g., https://gridcf.org/gct-docs/6.2/gridftp/admin/index.html#gridftp-config-overview), but also the man page says:

The configuration file for the GridFTP server is read from the following locations, in the given order. Only the first file found will be loaded:

* Path specified with the -c <configfile> command line option.
* $GLOBUS_LOCATION/etc/gridftp.conf
* /etc/grid-security/gridftp.conf

Which creates a false impression that if $GLOBUS_LOCATION is not defined, /etc/gridftp.conf will be read. But in fact it isn't the case:

tmp_gl = getenv("GLOBUS_LOCATION");
if(tmp_gl)
{
rc = snprintf(tmp_str, PATH_MAX, "%s/etc/gridftp.conf", tmp_gl);
if(rc > 0)
{
local_config_file = tmp_str;
}
}

Later, local_config_file does become (typically) /etc/gridftp.conf:

if(local_config_file == NULL && !argv_only)
{
globus_eval_path("${sysconfdir}/gridftp.conf", &local_config_file);
}

However, this is only used for setting environment

rc = globus_l_gfs_config_load_envs_from_file(local_config_file);

But contrary to global_config_file, it is NOT parsed by globus_l_gfs_config_load_config_file().

Most confusing, in the log gridftp then happily reports that /etc/gridftp.conf was used...

Regards,
Evgeny

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants