other:newppl:starting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
other:newppl:starting [2023/11/07 09:12] jypeter [Using existing information] Added other useful numbers |
other:newppl:starting [2024/04/03 11:33] jypeter [Available servers] Added getlogin and getenv Python example |
||
|---|---|---|---|
| Line 109: | Line 109: | ||
| * [[https://intranet.lsce.ipsl.fr/informatique/en/orme/imprimantes.php|Printers]] | * [[https://intranet.lsce.ipsl.fr/informatique/en/orme/imprimantes.php|Printers]] | ||
| - | ===== Accessing the CEA Saclay intranet and other CEA web sites with vpnssl ===== | + | ===== Accessing the CEA Saclay intranet and other CEA web sites from a browser ===== |
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| - | It used to be possible to access the CEA Saclay intranet by just clicking on http://www-saclay.cea.fr/ from any computer on the LSCE network. | + | LSCE is on the Paris-Saclay network (and **not on the CEA network**) |
| - | This is **not possible** anymore, now that LSCE is on the Paris-Saclay network (and not on the CEA network) | + | It is therefore **not possible** to access the //CEA Saclay// intranet by just clicking on http://www-saclay.cea.fr/ from a computer on the LSCE wired network (or //eduroam//, or any network outside CEA) |
| </WRAP> | </WRAP> | ||
| Use the following steps: | Use the following steps: | ||
| - Start Chrome (or try another browser) | - Start Chrome (or try another browser) | ||
| - | - Open the following link: https://vpnssl.cea.fr/ | + | * it is even better if you use a [[https://support.google.com/chrome/answer/95464?hl=en|Private/Incognito window]] to do this |
| - | * ignore the security errors | + | - Open the following link: https://vpn.cea.fr/ |
| + | * ignore the possible security/certificate errors | ||
| * this link will work from the Paris Saclay network, and ANY other location (e.g. home) OUTSIDE of CEA | * this link will work from the Paris Saclay network, and ANY other location (e.g. home) OUTSIDE of CEA | ||
| - Use your initials and badge number as the **login** (e.g. "//James Bond//" => "**jb007007**") and the number supplied by the //activIDentity// keyring, followed by your 4 digits personal code, as your **password** | - Use your initials and badge number as the **login** (e.g. "//James Bond//" => "**jb007007**") and the number supplied by the //activIDentity// keyring, followed by your 4 digits personal code, as your **password** | ||
| Line 129: | Line 130: | ||
| * ... | * ... | ||
| - Click on //logout// when you are done | - Click on //logout// when you are done | ||
| + | * ... and close your browser //Incognito// window if you used one | ||
| ===== Setting up your desktop computer ===== | ===== Setting up your desktop computer ===== | ||
| Line 218: | Line 220: | ||
| $ hostname | $ hostname | ||
| obelix5</code> | obelix5</code> | ||
| + | * In a python script, you can use the following to get some information | ||
| + | * <code>>>> import os | ||
| + | >>> os.getlogin(), os.getenv('HOST') | ||
| + | ('mylogin', 'obelix5')</code> | ||
| * **[[https://intranet.lsce.ipsl.fr/informatique/en/calcul/batch.php|The LSCE cluster]]** (aka the //batch system//)\\ Use this cluster for **//heavy duty// programs**, rather than killing the multi-users interactive servers | * **[[https://intranet.lsce.ipsl.fr/informatique/en/calcul/batch.php|The LSCE cluster]]** (aka the //batch system//)\\ Use this cluster for **//heavy duty// programs**, rather than killing the multi-users interactive servers | ||
| Line 270: | Line 276: | ||
| </code> | </code> | ||
| | | ||
| - | The top lines give you some summary information about the system, but you should monitor the memory usage (''VIRT'' and ''RES''), ''CPU'' and ''TIME'' columns. By default, ''top'' will will put the processes using the more CPU at the top (as shown above). You can see above that the ''emacs'' text editor has clearly crashed, because it should not use 100% CPU for such a long time | + | The top lines give you some summary information about the system, but you should monitor the memory usage (''VIRT'' and ''RES''), ''CPU'' and ''TIME+'' columns. By default, ''top'' will will put the processes using the more CPU at the top (as shown above). You can see above that the ''emacs'' text editor has clearly crashed, because it should not use 100% CPU for such a long time |
| + | |||
| + | * The ''TIME+'' information is in //minutes// (e.g. ''5432:01'' means //5432 minutes and 1 second//, ''25:15.20'' means //25 minutes, 15 seconds and 20% of 1 second//) | ||
| + | |||
| + | * Memory usage: | ||
| + | * ''%MEM'' (Kb): percentage of the total available **physical memory** used by a process. This is based on ''RES'', the **non-swapped physical memory** used by a process | ||
| + | * ''VIRT'' (Kb): total amount of **virtual memory** (i.e. memory temporarily swapped/saved to disk) used by a process. It includes all code, data and shared libraries plus pages that have been swapped out and pages that have been mapped but not used | ||
| + | * The ''free'' command can display the memory usage of a server at a given time. ''available'' is an estimation of how much memory is available for starting new applications, without swapping | ||
| + | * <code> % free -ht | ||
| + | total used free shared buff/cache available | ||
| + | Mem: 62G 1.5G 56G 11M 5.0G 60G | ||
| + | Swap: 62G 1.7G 60G | ||
| + | Total: 125G 3.3G 116G</code> | ||
| If you type ''M'', the processes will be sorted my memory usage, as shown below | If you type ''M'', the processes will be sorted my memory usage, as shown below | ||
| Line 286: | Line 304: | ||
| | **q** | Quit | | | **q** | Quit | | ||
| - | | **c** | Display the command line options of the running processes| | + | | **c** | Display the command line options of the running processes | |
| | **u** | List only the processes of a specific user | | | **u** | List only the processes of a specific user | | ||
| + | | **M** | Sort by memory usage (''%MEM'' columun) | | ||
| + | | **P** | Sort by CPU usage (''%CPU'' columun) (Default) | | ||
| + | |||
| + | ==== Using the kill command to terminate processes ==== | ||
| + | |||
| + | FIXME | ||
| + | |||
| + | ''kill proc_number'' | ||
| + | |||
| + | ''kill -9 -1'' | ||
| + | ''qdel'' | ||
| ===== Which disks should you use? ===== | ===== Which disks should you use? ===== | ||
| Line 394: | Line 423: | ||
| ...</code> | ...</code> | ||
| + | FIXME Add something about ''df'' | ||
| ===== Which programs should you use? ===== | ===== Which programs should you use? ===== | ||
| Line 471: | Line 501: | ||
| There are **lots of text editors available** on Linux computers/servers (''emacs'', ''nano'', ''vi'', ''vim'', ''gvim'', ''gedit'', ...). You can use them: | There are **lots of text editors available** on Linux computers/servers (''emacs'', ''nano'', ''vi'', ''vim'', ''gvim'', ''gedit'', ...). You can use them: | ||
| + | |||
| * In basic **text terminals** | * In basic **text terminals** | ||
| - | * useful if you are in a hurry, and/or working on a remote server with a bad network connection or have no local [[other:x_conf|X server]] running | + | * **If you only need to read a text file**, use a //pager// like [[http://www.greenwoodsoftware.com/less|less]] (or ''more''): ''less my_text_file.txt'' |
| - | * you should know the basic commands and shortcuts! Some text editors (e.g ''nano'') fortunately display some help at the bottom of the screen | + | * ''SPACE'' goes down one page |
| + | * ''b'' (//back//) goes back one page | ||
| + | * ''/STRING'' looks for ''STRING'' in the text (then ''n''ext, ''p''revious, ''q''uit) | ||
| + | * ''q'' exits | ||
| + | * **[[#gnu_nano|nano]] is probably the easiest editor in text mode** to use! | ||
| + | * Useful if you are in a hurry, and/or working on a remote server with a bad network connection or have no local [[other:x_conf|X server]] running | ||
| + | * You should know the basic commands and shortcuts! | ||
| * With a **full Graphical User Interface** (aka //GUI//) allowing you to use the mouse+menus/buttons/etc... | * With a **full Graphical User Interface** (aka //GUI//) allowing you to use the mouse+menus/buttons/etc... | ||
| Line 482: | Line 519: | ||
| <note important>Read the **dedicated [[other:emacs_doc|Using emacs]] page**, and become a power user!</note> | <note important>Read the **dedicated [[other:emacs_doc|Using emacs]] page**, and become a power user!</note> | ||
| + | === Gnu nano === | ||
| + | |||
| + | <note tip>Gnu [[https://www.nano-editor.org/|nano]] is probably the easiest text editor in text mode to use!</note> | ||
| + | You can easily view/edit a file by just typing ''nano my_text_file.txt'' in a terminal, and looking at the instructions displayed at the bottom of the screen (e.g. ''^X Exit'' means that you can exit the editor by typing ''CTRL-X'') | ||
| === vi (vim, gvim) === | === vi (vim, gvim) === | ||
other/newppl/starting.txt · Last modified: 2024/04/24 12:37 by jypeter
