.bashrc Do's and Don'ts - Revision history

S Braun: /* Autoedits / Conda */

2025-01-09T15:22:53Z

Autoedits / Conda

← Older revision		Revision as of 17:22, 9 January 2025
Line 31:		Line 31:
	== Autoedits / Conda ==		== Autoedits / Conda ==

	There is some software (e.g. ~~conda~~) ~~which~~ automatically modifies .bashrc. Make sure to have a copy of your .bashrc and test after installing ~~software~~ ~~like this~~		There is some software (e.g. Conda) that automatically modifies .bashrc. These modifications may interfere with the proper functioning of e.g. Python from Lmod modules or the Jupyter modules. Make sure you have a copy of your .bashrc and test it after installing such software.

K Siegmund: /* Do's */

2024-11-05T10:58:40Z

Do's

← Older revision		Revision as of 12:58, 5 November 2024
Line 26:		Line 26:
	HISTIGNORE="?:??" # dont store one and two letter commands		HISTIGNORE="?:??" # dont store one and two letter commands
	</syntaxhighlight>		</syntaxhighlight>

			* maybe make your rm / cp commands safer by aliasing to -i <code> alias rm 'rm -i'</code>

	== Autoedits / Conda ==		== Autoedits / Conda ==

K Siegmund at 09:15, 5 November 2024

2024-11-05T09:15:42Z

← Older revision		Revision as of 11:15, 5 November 2024
Line 26:		Line 26:
	HISTIGNORE="?:??" # dont store one and two letter commands		HISTIGNORE="?:??" # dont store one and two letter commands
	</syntaxhighlight>		</syntaxhighlight>

			== Autoedits / Conda ==

			There is some software (e.g. conda) which automatically modifies .bashrc. Make sure to have a copy of your .bashrc and test after installing software like this

K Siegmund: /* Dont's */

2024-11-05T09:08:09Z

Dont's

← Older revision		Revision as of 11:08, 5 November 2024
Line 3:		Line 3:
	You can add commands that you want to run every time at login and when starting a job by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.		You can add commands that you want to run every time at login and when starting a job by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.

	== ~~Dont~~'s ==		== Don'ts ==

	* don't forget to test your changes before you log out (log in on a second shell)		* don't forget to test your changes before you log out (log in on a second shell)
	* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment		* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment
	* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc, unless you know exactly what you're doing		* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc, unless you know exactly what you're doing
	*		*

	== Do's ==		== Do's ==

K Siegmund at 09:07, 5 November 2024

2024-11-05T09:07:06Z

← Older revision		Revision as of 11:07, 5 November 2024
Line 5:		Line 5:
	== Dont's ==		== Dont's ==

	* don't forget to test your changes before you log out		* don't forget to test your changes before you log out (log in on a second shell)
	* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment		* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment
	* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc, unless you know exactly what you're doing		* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc, unless you know exactly what you're doing
Line 11:		Line 11:

	== Do's ==		== Do's ==
			* make a copy of your .bashrc before making large changes

	* '''test''' your changes to .bashrc before you log out		* '''test''' your changes to .bashrc before you log out
	* add command aliases or bash functions in .bashrc - example: <code> alias l='ls -la' </code>		* add command aliases or bash functions in .bashrc - example: <code> alias l='ls -la' </code>

H Winkhardt: Tippfehler

2024-10-08T13:53:50Z

Tippfehler

← Older revision		Revision as of 15:53, 8 October 2024
Line 1:		Line 1:
	.bashrc and .profiles are files that are sourced when you log in, they set some important variables that make your shell function at a specific site setup.		.bashrc and .profiles are files that are sourced when you log in, they set some important variables that make your shell function at a specific site setup.

	You can add commands that you want to run every time by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.		You can add commands that you want to run every time at login and when starting a job by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.

	== ~~Donts~~'s ==		== Dont's ==

	* don't forget to test your changes before you log out		* don't forget to test your changes before you log out
	* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment		* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment
	* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc ~~except if~~ you know exactly what you're doing		* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc, unless you know exactly what you're doing
	*		*

K Siegmund at 12:40, 8 October 2024

2024-10-08T12:40:21Z

← Older revision		Revision as of 14:40, 8 October 2024
Line 1:		Line 1:
	.bashrc and .profiles are files that are sourced when you log in.		.bashrc and .profiles are files that are sourced when you log in, they set some important variables that make your shell function at a specific site setup.

	You can add commands that you want to run every time by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.		You can add commands that you want to run every time by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.

K Siegmund at 12:39, 8 October 2024

2024-10-08T12:39:31Z

← Older revision		Revision as of 14:39, 8 October 2024
Line 16:		Line 16:
	* add a local ~/bin or similar to $PATH if needed		* add a local ~/bin or similar to $PATH if needed
	* improve your terminal command history experience:		* improve your terminal command history experience:
	<~~source~~ lang=bash>		<syntaxhighlight lang=bash>
	shopt -s histappend # append to the history file, don't overwrite it		shopt -s histappend # append to the history file, don't overwrite it
	shopt -s direxpand # expand dirs before trying to expand filenames		shopt -s direxpand # expand dirs before trying to expand filenames
Line 25:		Line 25:
	HISTCONTROL=ignoreboth:erasedups # dont store duplicates and ignore lines starting with white space		HISTCONTROL=ignoreboth:erasedups # dont store duplicates and ignore lines starting with white space
	HISTIGNORE="?:??" # dont store one and two letter commands		HISTIGNORE="?:??" # dont store one and two letter commands
			</syntaxhighlight>
	</source>

K Siegmund: Created page with ".bashrc and .profiles are files that are sourced when you log in. You can add commands that you want to run every time by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder. == Donts's == * don't forget to test your changes before you log out * don't put `module load` commands in .bashrc, modules may make changes that break the default system environment * don't put LD_PRELOAD or LIBRARY..."

2024-10-08T12:36:54Z

Created page with ".bashrc and .profiles are files that are sourced when you log in. You can add commands that you want to run every time by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder. == Donts's == * don't forget to test your changes before you log out * don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment * don't put LD_PRELOAD or LIBRARY..."

New page

.bashrc and .profiles are files that are sourced when you log in.

You can add commands that you want to run every time by adding lines to these files, but you can also make mistakes that make your life or the life of the cluster teams harder.

== Donts's ==

* don't forget to test your changes before you log out
* don't put <code> module load </code> commands in .bashrc, modules may make changes that break the default system environment
* don't put LD_PRELOAD or LIBRARY_PATH in your .bashrc except if you know exactly what you're doing
*

== Do's ==

* '''test''' your changes to .bashrc before you log out
* add command aliases or bash functions in .bashrc - example: <code> alias l='ls -la' </code>
* add a local ~/bin or similar to $PATH if needed
* improve your terminal command history experience:
<source lang=bash>
shopt -s histappend # append to the history file, don't overwrite it
shopt -s direxpand # expand dirs before trying to expand filenames
HISTSIZE=1000000 # number of commands stored in one terminal session
HISTFILESIZE=20000000 # number of commmands stored in file
HISTFILE="$HOME"/.bash_history_$USER # prevent file truncation by bash sessions that did not read in .bashrc
PROMPT_COMMAND="history -a" # save history after every command
HISTCONTROL=ignoreboth:erasedups # dont store duplicates and ignore lines starting with white space
HISTIGNORE="?:??" # dont store one and two letter commands
</source>