From 1b723995b7417b82907948520251a2c4341aeb16 Mon Sep 17 00:00:00 2001 From: Aidan Rosberg Date: Thu, 23 Apr 2026 11:22:51 -0400 Subject: [PATCH 1/2] Fix admonition rendering, switch to inline code block for better readability --- docs/faqs_tips.md | 46 ++++++++++++++++++++++------------------------ 1 file changed, 22 insertions(+), 24 deletions(-) diff --git a/docs/faqs_tips.md b/docs/faqs_tips.md index b2bf52c..6ef83b9 100644 --- a/docs/faqs_tips.md +++ b/docs/faqs_tips.md @@ -10,48 +10,48 @@ after ssh login to CERN lxplus machines. /usr/bin/xauth: timeout in locking authority file /afs/cern.ch/user/y/yesw/.Xauthority ``` -And it is very annoying that you have to run "kinit" again after ssh login. +And it is very annoying that you have to run `kinit` again after ssh login. To avoid the above trouble, you can: -- either add the option **"-k"** to the ssh command. -- or add **"GSSAPIDelegateCredentials yes"** into ~/.ssh/config on the local +- either add the option `-k` to the ssh command. +- or add `GSSAPIDelegateCredentials yes` into `~/.ssh/config` on the local computer. ### Sharing the same kerberos token among the home clusters By default, the kerberos token is cached locally on each individual machine, and -you have to run kinit each time on a different node. If those machines share the -same home directory, you can define the envvar **KRB5CCNAME** to -**$HOME/krb5cc\_`id -u`** prior to running **kinit**. So you would have a valid +you have to run `kinit` each time on a different node. If those machines share the +same home directory, you can define the envvar `KRB5CCNAME` to +`$HOME/krb5cc_$(id -u)` prior to running `kinit`. So you would have a valid kerberos token on other machines too. For example, once you have obtained a valid CERN kerberos on one BNL attsub machine, you can also access CERN EOS on other attsub machines without running -"kinit" again. +`kinit` again. ### Sharing one envvar KRB5CCNAME among multiple kerberos principals -The envvar **KRB5CCNAME** points to a file, it could only hold one kerberos +The envvar `KRB5CCNAME` points to a file, it could only hold one kerberos prinpical. However, you can define it to point to a directory instead, then it could be used for multiple kerberos pricipals. That is: -``` - export KRB5CCNAME=DIR:$HOME/.krb5cc +```sh +export KRB5CCNAME=DIR:$HOME/.krb5cc ``` -Please note the prefix **"DIR:"** before the directory name. And you need create -the directory **$HOME/.krb5cc** in advance. +Please note the prefix `DIR:` before the directory name. And you need create +the directory `$HOME/.krb5cc` in advance. ### How to set up python3 env from CVMFS? -Run **showVersions python** after the ALRB setup (that is, running -_setupATLAS_). It will show the available python versions on CVMFS. +Run `showVersions python` after the ALRB setup (that is, running +`setupATLAS`). It will show the available python versions on CVMFS. -Then you can pick up one suitable for you, says, _3.8.8-x86_64-centos7_. So you -can run **lsetup "python 3.8.8-x86_64-centos7"** to set up that python3. +Then you can pick up one suitable for you, says, `3.8.8-x86_64-centos7`. So you +can run `lsetup "python 3.8.8-x86_64-centos7"` to set up that python3. ### How to set up Rucio with python3? @@ -60,9 +60,9 @@ python3? You can run the following: -``` - export RUCIO_PYTHONBIN=python3 - lsetup rucio +```sh +export RUCIO_PYTHONBIN=python3 +lsetup rucio ``` ### How to transfer QR code from Google Authenticator to other devices? @@ -88,7 +88,7 @@ Authenticator, then add the secret code into other devices in the following: 4. Call [this script on github](https://github.com/scito/extract_otp_secret_keys): -``` +```sh python extract_otp_secret_keys.py -p example_export.txt ``` @@ -437,6 +437,7 @@ pkill -f my_script.py pkill -u $USER -f "jupyter" ``` + !!! warning "Be Careful with pkill" `pkill` can terminate multiple processes at once. Always double-check what @@ -447,7 +448,4 @@ pkill -u $USER -f "jupyter" pgrep -u $USER -f "pattern" # Then kill: pkill -u $USER -f "pattern" - -``` - -``` + ``` From e402e261791b25028b9a5ece75b538e743d57b82 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Thu, 23 Apr 2026 15:29:34 +0000 Subject: [PATCH 2/2] style: pre-commit fixes --- docs/faqs_tips.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/faqs_tips.md b/docs/faqs_tips.md index 6ef83b9..5b77150 100644 --- a/docs/faqs_tips.md +++ b/docs/faqs_tips.md @@ -21,8 +21,8 @@ To avoid the above trouble, you can: ### Sharing the same kerberos token among the home clusters By default, the kerberos token is cached locally on each individual machine, and -you have to run `kinit` each time on a different node. If those machines share the -same home directory, you can define the envvar `KRB5CCNAME` to +you have to run `kinit` each time on a different node. If those machines share +the same home directory, you can define the envvar `KRB5CCNAME` to `$HOME/krb5cc_$(id -u)` prior to running `kinit`. So you would have a valid kerberos token on other machines too. @@ -42,13 +42,13 @@ used for multiple kerberos pricipals. That is: export KRB5CCNAME=DIR:$HOME/.krb5cc ``` -Please note the prefix `DIR:` before the directory name. And you need create -the directory `$HOME/.krb5cc` in advance. +Please note the prefix `DIR:` before the directory name. And you need create the +directory `$HOME/.krb5cc` in advance. ### How to set up python3 env from CVMFS? -Run `showVersions python` after the ALRB setup (that is, running -`setupATLAS`). It will show the available python versions on CVMFS. +Run `showVersions python` after the ALRB setup (that is, running `setupATLAS`). +It will show the available python versions on CVMFS. Then you can pick up one suitable for you, says, `3.8.8-x86_64-centos7`. So you can run `lsetup "python 3.8.8-x86_64-centos7"` to set up that python3.