Consider dropping `xrd.network keepalive` from example configs

Open Beginner friendly
#58 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Domain
documentation, tooling

Research direction

Inspect the three named files: doc/diopside/manual/configuration.rst, misc/etc/xrd.cf.fst, and misc/etc/eos/config/fst/fst, and compare their xrd.network keepalive entries with the referenced XRootD documentation. Confirm that keepalive is already the default and that no kaparms guidance is needed; done means the redundant entries are removed consistently from all three files.

Written by the indexing model from the issue text.

Description

According to some docs, for example https://indico.cern.ch/event/523410/contributions/2355670/attachments/1367325/2071860/XWS-Tokyo-Status.pdf, keepalive is the default in XRootD for about 10 years.

So any upcoming EOS release can savely assume keepalive being already enabled, right?

So I'd suggest to just remove xrd.network keepalive from

  • doc/diopside/manual/configuration.rst
  • misc/etc/xrd.cf.fst
  • misc/etc/eos/config/fst/fst

One could argue that maybe some admins want to set the kaparms suboption? I think, that's advanced use (and it's currently not even mentioned in the eos repo!).

Dominant language
C++
Stars
250
Forks
47
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cern-eos/eos

All issues in cern-eos/eos

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.