Translations:Utiliser des modules/3/en: Difference between revisions

Translations:Utiliser des modules/3/en (view source)

455 bytes added , 6 years ago

no edit summary

Bureaucrats, cc_docs_admin, cc_staff

2,318

edits

Revision as of 19:33, 6 December 2016 (view source) Rdickson (talk \| contribs) No edit summary ← Older edit		Latest revision as of 19:07, 18 June 2018 (view source) Stubbsda (talk \| contribs) No edit summary
Line 1:		Line 1:
	A "modulefile" contains the information needed to make an application or library available in the user's login session. Typically a module file contains instructions that modify or initialize environment variables such as <code>PATH</code> and <code>LD_LIBRARY_PATH</code> in order to use different installed programs.		A "modulefile" contains the information needed to make an application or library available in the user's login session. Typically a module file contains instructions that modify or initialize environment variables such as <code>PATH</code> and <code>LD_LIBRARY_PATH</code> in order to use different installed programs. Note that the simple fact of loading a module doesn't execute the software in question. To learn the name of the program binary or the syntax for its use, you should read the documentation for this software. By using the <tt>module</tt> command, you shouldn't normally need to know the exact location or path of the software or library but you can nevertheless see such details about the module by means of the command <tt>module show <module-name></tt>.