-
Notifications
You must be signed in to change notification settings - Fork 39
some small fixes to the client #459
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: main
Are you sure you want to change the base?
some small fixes to the client #459
Conversation
@@ -82,7 +82,7 @@ which should contain something like: | |||
|
|||
``` { .ini .copy } | |||
CVMFS_CLIENT_PROFILE="single" # a single node setup, not a cluster | |||
CVMFS_QUOTA_LIMIT=10000 | |||
CVMFS_QUOTA_LIMIT=10000 # 10 GB of local client cache, shared |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CVMFS_QUOTA_LIMIT=10000 # 10 GB of local client cache, shared | |
CVMFS_QUOTA_LIMIT=10000 # 10 GB of local client cache, shared across repos |
!!! danger "never heard anyone call them parameter files? maybe not needed?" | ||
|
||
CernVM-FS can be configured through a *hierarchy* of configuration files (sometimes also referred to as | ||
parameter files), which can be located under either `/etc/cvmfs`, or the [CernVM-FS configuration repository]( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!!! danger "never heard anyone call them parameter files? maybe not needed?" | |
CernVM-FS can be configured through a *hierarchy* of configuration files (sometimes also referred to as | |
parameter files), which can be located under either `/etc/cvmfs`, or the [CernVM-FS configuration repository]( | |
CernVM-FS can be configured through a *hierarchy* of configuration files, | |
which can be located under either `/etc/cvmfs`, or the [CernVM-FS configuration repository]( |
@@ -226,6 +231,8 @@ update the `autofs` configuration. | |||
|
|||
### Recommendations for `autofs` {: #autofs } | |||
|
|||
!!! danger "is this still recommended?" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the linked issue does no longer apply, I think. There may be circumstances with bind-mounts into containers, let me double-check that
@@ -351,6 +358,8 @@ To start using EESSI just [source the initialisation script](../eessi/using-eess | |||
source /cvmfs/software.eessi.io/versions/2023.06/init/bash | |||
``` | |||
|
|||
!!! danger "update link to latest version? maybe add to eessi a symlink /cvmfs/software.eessi.io/versions/latest/init/bash" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!!! danger "update link to latest version? maybe add to eessi a symlink /cvmfs/software.eessi.io/versions/latest/init/bash" |
For now this is still the only version we had. We actually used to have a latest
symlink, but we stopped doing that because figuring out when to update the target of that is ... challenging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds reasonable. And for the tutorial even an old version would work.
please DO NOT MERGE until you have taken a decision on and removed comments marked with
!!! danger