https://itp.uni-frankfurt.de/wiki-it/api.php?action=feedcontributions&feedformat=atom&user=ThomasIT Service Wiki - User contributions [en]2026-05-13T19:21:03ZUser contributionsMediaWiki 1.31.1https://itp.uni-frankfurt.de/wiki-it/index.php?title=VPN_Access&diff=712VPN Access2017-05-08T11:17:38Z<p>Thomas: </p>
<hr />
<div>To get full access to our network from external locations we provide a VPN access based on openvpn. This is free software and part of every Linux distribution. The following guide has been tested with Ubuntu 12.04 to 17.04. It is available for Windows and MacOS too.<br />
<br />
=== Install OpenVPN === <br />
<br />
It is not part of the default installation, but can easily installed using apt. Enter the following commands:<br />
<br />
sudo apt-get install openvpn<br />
<br />
The requieres to enter your password to get super user privileges.<br />
<br />
=== Command line configuration ===<br />
<br />
This is fast and easy but requires to enter commands. Create or download [http://th.physik.uni-frankfurt.de/~thw/vpn/all-via-itp.ovpn] the config file and store it anywhere you like:<br />
<br />
<pre><br />
client<br />
dev tap<br />
proto udp<br />
nobind<br />
remote vpn.th.physik.uni-frankfurt.de<br />
verify-x509-name vpn.th.physik.uni-frankfurt.de name<br />
remote-cert-tls server<br />
resolv-retry infinite<br />
auth-user-pass<br />
ca private-ca-itp.crt<br />
redirect-gateway def1 <br />
</pre><br />
<br />
Download our CA (Certificate of Authority) [http://th.physik.uni-frankfurt.de/~thw/vpn/private-ca-itp.crt] and store it in the same place. This file is needed for verifcation the authenticity of the server.<br />
<br />
This configuration routes all traffic trough ITP, this is usful if you want to download papers, which are restricted to the university network.<br />
The second examples only routes the traffic going directly to the ITP trough the VPN and leaves your default gateway untouched. The only difference is the missing 'redirect-gateway' statment [http://th.physik.uni-frankfurt.de/~thw/vpn/itp.vpn].<br />
<br />
<pre><br />
<br />
client<br />
dev tap<br />
proto udp<br />
nobind<br />
remote vpn.th.physik.uni-frankfurt.de<br />
verify-x509-name vpn.th.physik.uni-frankfurt.de name<br />
remote-cert-tls server<br />
resolv-retry infinite<br />
auth-user-pass<br />
ca private-ca-itp.crt<br />
</pre><br />
<br />
=== Start the VPN connection ===<br />
<br />
Open a terminal and change to the path where the vpn config file is stored. Start the connection with<br />
<br />
sudo openvpn itp.ovpn<br />
<br />
where itp.ovpn is the name of the config file. openvpn needs root access, therefore you must enter your local password for sudo. After this you have to enter your ITP credentials (Username and Password).<br />
<br />
If everything went fine the output will look like:<br />
<br />
<pre><br />
Fri Dec 7 15:03:00 2012 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).<br />
Fri Dec 7 15:03:00 2012 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables<br />
Fri Dec 7 15:03:00 2012 UDPv4 link local: [undef]<br />
Fri Dec 7 15:03:00 2012 UDPv4 link remote: [AF_INET]141.2.246.2:1194<br />
Fri Dec 7 15:03:00 2012 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this<br />
Fri Dec 7 15:03:00 2012 [FIAS-ITP_Generic_VPN_Service] Peer Connection Initiated with [AF_INET]141.2.246.2:1194<br />
Fri Dec 7 15:03:02 2012 TUN/TAP device tap0 opened<br />
Fri Dec 7 15:03:02 2012 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0<br />
Fri Dec 7 15:03:02 2012 /sbin/ifconfig tap0 10.63.131.1 netmask 255.255.0.0 mtu 1500 broadcast 10.63.255.255<br />
Fri Dec 7 15:03:02 2012 Initialization Sequence Completed<br />
</pre><br />
<br />
Termiate the session by pressing Ctrl-C in this terminal.<br />
<br />
=== Hacking around firewalls ===<br />
<br />
If you have problems with firewalls, we provide some oder ports und protocols to circumvent these firewalls<br />
<br />
{|border="1"<br />
|-<br />
!Proto<br />
!Port<br />
|-<br />
| tcp<br />
| 1194<br />
|-<br />
|tcp<br />
| 80<br />
|-<br />
|udp<br />
|53<br />
|}</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=General_Information&diff=704General Information2017-02-27T09:57:05Z<p>Thomas: </p>
<hr />
<div>From the users point of view, our setup is very easy. You don't have to learn many hostnames. You just have to learn the domain name, which is '''th.physik.uni-frankfurt.de'''. This is called our virtual service address, and all services are accessed through this domain name.<br />
<br />
== Mail Setup ==<br />
<br />
We provide some mail programs preconfigured for our system. That are Thunderbird, alpine and mutt. If you want to use another program, you have the configure it by your self.<br />
<br />
=== Outgoing mail ===<br />
<br />
Outgoing mail has to be send to th.physik.uni-frankfurt.de. If you want to send from outside our network (from home etc.) you have to enable TLS (Transport Layer Security) and authenticate with your login name and password. Port for submission is 587. <br />
<br />
=== Incoming mail ===<br />
<br />
For incoming mail we provide IMAP support. IMAP works with the mail on the server an does not download it on your computer. The server 'th.physik.uni-frankfurt.de'. You have to use the SSL encryption, regardless if your inside or outside our network.<br />
<br />
=== Webmail ===<br />
<br />
There also the option to use our webmail front end: https://th.physik.uni-frankfurt.de/webmail/src/login.php<br />
<br />
=== Certificates ===<br />
<br />
We have now official certificates and you must not get any warning.<br />
<br />
== Thunderbird ==<br />
<br />
For Thunderbird we support autoconfiguration. After entering you mail address and password. Thundbird should automatically detect the correct setting. The final dialog should lock like this:<br />
<br />
[[File:Thunderbird-Setup.png]]</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=File:Thunderbird-Setup.png&diff=703File:Thunderbird-Setup.png2017-02-27T09:52:59Z<p>Thomas: </p>
<hr />
<div></div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Archiving_Data&diff=701Archiving Data2016-12-15T12:24:13Z<p>Thomas: </p>
<hr />
<div>The backup and archive service is provided by the HRZ through the IBM Tivoli Storage Manager (TSM). In addition to our nightly backups, we provide the archiving service for individual users. Archiving means: The data is transfered to HRZ and stored on tape. In opposite to a backup, the local data can been deleted. The data in the archive are stored for ten years and then automatically deleted.<br />
<br />
The archive client is installed on our login server.<br />
<br />
== Archiving Data ==<br />
<br />
Open a ssh connection to our login server:<br />
<br />
$ ssh th.physik.uni-frankfurt.de<br />
<br />
The command line tool is called 'dsmc' (for historical reason it stand for 'Distributed Storage Manager Client'). It supports interactive operation (call without arguments) and non interactive with command line arguments.<br />
<br />
To archive a single file (eg. a tar archive) just call:<br />
<br />
$ dsmc archive FILENAME<br />
<br />
To archive a complete tree call<br />
<br />
$ dsmc archive -subdir=yes DIRECTORY/<br />
<br />
All files are stored and queried with the complete path name.<br />
<br />
If the files are successfully archived, they can be deleted from the local disk.<br />
<br />
== Querying archived data ==<br />
<br />
To see the archives data from the current directory:<br />
<br />
dsmc query archive "*"<br />
<br />
Use the option '-subdir=yes' to get a complete list of files.<br />
<br />
== Retrieving archived data ==<br />
<br />
If you need the archived data back, enter<br />
<br />
dsmc retrieve FILESPEC<br />
<br />
== Deleting archived data ==<br />
<br />
You have th permission to delete your own data, before the end of the archive period of ten years with the command:<br />
<br />
dsmc delete archive FILESPEC<br />
<br />
== Further Reading: ==<br />
<br />
* HRZ Page (German) [http://www.rz.uni-frankfurt.de/services/tsm/index.html]<br />
* IBM Tivoli Storage Manager Manual (english, pdf) [http://th.physik.uni-frankfurt.de/~thw/b_ba_guide_unx_lnx_en.pdf]</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Storage_and_Backup&diff=700Storage and Backup2016-12-15T12:22:43Z<p>Thomas: </p>
<hr />
<div>The storage servers and importand hosts (like the login server) are connected with infiniband. Therefor prefer this host for doing larger file I/O, it will be much faster.<br />
<br />
== Storage ==<br />
<br />
There are different file systems with different lifetime and redundancy which you can use to store your data. <br />
<br />
;your home directory<br />
:This is your primary directory where all settings, your Mail and other important data is saved. It is mounted on every host to /home/YOUR_LOGIN. A backup is done nightly. This file system has an individual limit which you can check with the command 'df'. In change to earlier setups it has no soft limit which you can exceed for a few days. If you have problems with graphical logins or reading mails, first check your disk space.<br />
<br />
;/tmp&nbsp;<br />
:This is the counterpart to your home. It is located on the local disk and should be used for temporary data. Unused files are delete after 14 days.<br />
<br />
;/home/work-itp<br />
:This directory is globally accessible and can be used by everyone for minor important data which are not worth to be backed up or simply to large for home. This files are not deleted, but if the disk is full we tell you to delete some files. It runs on a raid6 system, that means a disk failure will not result in data loss. It is also served by a dedicated machine (magnum) and heavy load does not affect the home directories. It is connected with a 10 GbE-Interface to the central switch in the server room.<br />
<br />
:If you want to use this space please create a sub directory with you login name. All other files and directories will be delete without notice.<br />
<br />
;/data (some hosts only)<br />
:This is the local disk (mostly on machines on the first floor). It has the same level like /tmp except that it isn't deleted automatically. Data on this partition is silently deleted when reinstalling or upgrading the machine.<br />
<br />
== Backup ==<br />
<br />
Backups of the home directory and several other important system directories is done nightly.<br />
<br />
*There are held '''3''' generations of a file.<br />
*Overwritten files are stored for '''90''' days<br />
*A deleted file is stored for '''90''' days<br />
<br />
If you have delete some files and want them restored, please contact the system administrator.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Storage_and_Backup&diff=699Storage and Backup2016-12-15T12:22:06Z<p>Thomas: </p>
<hr />
<div>The storage servers and importand hosts (like the login server) are connected with infiniband. Therefor prefer this host for doing larger file I/O, it will be much faster.<br />
<br />
== Storage ==<br />
<br />
There are different file systems with different lifetime and redundancy which you can use to store your data. <br />
<br />
;your home directory<br />
:This is your primary directory where all settings, your Mail and other important data is saved. It is mounted on every host to /home/YOUR_LOGIN. A backup is done nightly. This file system has an individual limit which you can check with the command 'df'. In change to earlier setups it has no soft limit which you can exceed for a few days. If you have problems with graphical logins or reading mails, first check your disk space.<br />
<br />
;/tmp&nbsp;<br />
:This is the counterpart to your home. It is located on the local disk and should be used for temporary data. Unused files are delete after 14 days.<br />
<br />
;/home/work-itp<br />
:This directory is globally accessible and can be used by everyone for minor important data which are not worth to be backed up or simply to large for home. This files are not deleted, but if the disk is full we tell you to delete some files. It runs on a raid6 system, that means a disk failure will not result in data loss. It is also served by a dedicated machine (magnum) and heavy load does not affect the home directories. It is connected with a 10 GbE-Interface to the central switch in the server room.<br />
<br />
:If you want to use this space please create a sub directory with you login name.<br />
<br />
;/data (some hosts only)<br />
:This is the local disk (mostly on machines on the first floor). It has the same level like /tmp except that it isn't deleted automatically. Data on this partition is silently deleted when reinstalling or upgrading the machine.<br />
<br />
== Backup ==<br />
<br />
Backups of the home directory and several other important system directories is done nightly.<br />
<br />
*There are held '''3''' generations of a file.<br />
*Overwritten files are stored for '''90''' days<br />
*A deleted file is stored for '''90''' days<br />
<br />
If you have delete some files and want them restored, please contact the system administrator.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=698Owncloud2016-12-15T12:19:15Z<p>Thomas: </p>
<hr />
<div>The Owncloud is now Nextcloud, a fork for that we expect a more vital development. Nextcloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Nextcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login.<br />
<br />
On our Linux installation the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the Nextcloud website [http://nextcloud.com].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Nextcloud Server has its own backup and an internal undo function. So there is basically no need the have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are three options we recommend:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
# Use the scratch disk /home/work-itp<br />
<br />
== Additional Help ==<br />
<br />
After login to the Owncloud server, you will find some example files and (important) the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write to the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=697Owncloud2016-12-15T12:17:32Z<p>Thomas: </p>
<hr />
<div>The Owncloud is now Nextcloud, a fork for that we expect a more vital development. Nextcloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Nextcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login.<br />
<br />
On our Linux installation the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://nextcloud.com].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need the have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options we recommend:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After login to the Owncloud server, you will find some example files and (important) the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write to the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=696Owncloud2016-12-15T12:16:57Z<p>Thomas: </p>
<hr />
<div>The Owncloud is now Nextcloud, a fork for that we expect a more vital development. Nextcloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Nextcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://nextcloud.com].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need the have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options we recommend:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After login to the Owncloud server, you will find some example files and (important) the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write to the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SAMBA_Service&diff=695SAMBA Service2016-12-15T10:58:11Z<p>Thomas: </p>
<hr />
<div>We've set up a whole new Samba service for you which is fully integrated into the LDAP service for authentication. If your account is old and you never have used SMB/CIFS service before, your account is missing the LDAP Attributes. If you have problems using this service, please contact us on trouble@th.physik.uni-frankfurt.de<br />
<br />
=== Windows 7 ===<br />
# Open Computer by clicking the Start button and then clicking "Computer".<br />
# Click "Map network drive".<br />
[[File:Win7_computer.PNG|thumb<br />
|Map network drive in Computer (Windows 7)]]<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at logon" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification. <br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
=== Windows 10 ===<br />
# Open File Explorer and on the left select "This PC".<br />
# Click the "Map network drive" button in the ribbon menu at the top. <br />
[[File:Win10_this_pc.PNG|thumb<br />
|Map network drive in This PC (Windows 10)]]<br />
# Then select "Map network drive." This is under the "Computer" tab, which should open automatically when you go to This PC, as above.<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at sign-in" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification.<br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
== Connect to SAMBA printers ==<br />
<br />
Connecting to printers work as above.<br />
<br />
=== Windows 7 ===<br />
# Open "Devices and Printers" by clicking the Start button and then, on the Start menu, clicking "Devices and Printers".<br />
# Click Add a printer.<br />
# In the "Add Printer" wizard, click "Add a network, wireless or Bluetooth printer". <br />
# Windows will search for available printers, but you want to click "The printer that I want isn't listed".<br />
[[File:printer_isnt_listed.PNG|thumb<br />
|The printer that I want isn't listed]]<br />
# Select "Select a shared printer by name" and type <code>\\samba-itp\PRINTERNAME</code> while PRINTERNAME stands for the name of the printer e.g. "psKyo2".<br />
# If prompted, install the printer driver on your computer by clicking "Install driver". <br />
# Complete the additional steps in the wizard, and then click "Finish".<br />
<br />
=== Windows 10 ===<br />
Coming Soon!</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SAMBA_Service&diff=694SAMBA Service2016-12-15T10:57:27Z<p>Thomas: </p>
<hr />
<div>We've set up a whole new Samba service for you which is fully integrated into upcoming LDAP service for authentication. If your account is old and you never have used SMB/CIFS service before, your account is missing the LDAP Attributes. If you have problems using this service, please contact us on trouble@th.physik.uni-frankfurt.de<br />
<br />
=== Windows 7 ===<br />
# Open Computer by clicking the Start button and then clicking "Computer".<br />
# Click "Map network drive".<br />
[[File:Win7_computer.PNG|thumb<br />
|Map network drive in Computer (Windows 7)]]<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at logon" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification. <br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
=== Windows 10 ===<br />
# Open File Explorer and on the left select "This PC".<br />
# Click the "Map network drive" button in the ribbon menu at the top. <br />
[[File:Win10_this_pc.PNG|thumb<br />
|Map network drive in This PC (Windows 10)]]<br />
# Then select "Map network drive." This is under the "Computer" tab, which should open automatically when you go to This PC, as above.<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at sign-in" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification.<br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
== Connect to SAMBA printers ==<br />
<br />
Connecting to printers work as above.<br />
<br />
=== Windows 7 ===<br />
# Open "Devices and Printers" by clicking the Start button and then, on the Start menu, clicking "Devices and Printers".<br />
# Click Add a printer.<br />
# In the "Add Printer" wizard, click "Add a network, wireless or Bluetooth printer". <br />
# Windows will search for available printers, but you want to click "The printer that I want isn't listed".<br />
[[File:printer_isnt_listed.PNG|thumb<br />
|The printer that I want isn't listed]]<br />
# Select "Select a shared printer by name" and type <code>\\samba-itp\PRINTERNAME</code> while PRINTERNAME stands for the name of the printer e.g. "psKyo2".<br />
# If prompted, install the printer driver on your computer by clicking "Install driver". <br />
# Complete the additional steps in the wizard, and then click "Finish".<br />
<br />
=== Windows 10 ===<br />
Coming Soon!</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SAMBA_Service&diff=693SAMBA Service2016-12-15T10:56:43Z<p>Thomas: </p>
<hr />
<div>We've set up a whole new Samba service for you which is fully integrated into upcoming LDAP service for authentication. If your account is old and you never have used SMB/CIFS service before your account is missing the LDAP Attributes. If you have problems using this service, please contact us on trouble@th.physik.uni-frankfurt.de<br />
<br />
=== Windows 7 ===<br />
# Open Computer by clicking the Start button and then clicking "Computer".<br />
# Click "Map network drive".<br />
[[File:Win7_computer.PNG|thumb<br />
|Map network drive in Computer (Windows 7)]]<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at logon" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification. <br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
=== Windows 10 ===<br />
# Open File Explorer and on the left select "This PC".<br />
# Click the "Map network drive" button in the ribbon menu at the top. <br />
[[File:Win10_this_pc.PNG|thumb<br />
|Map network drive in This PC (Windows 10)]]<br />
# Then select "Map network drive." This is under the "Computer" tab, which should open automatically when you go to This PC, as above.<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at sign-in" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification.<br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
== Connect to SAMBA printers ==<br />
<br />
Connecting to printers work as above.<br />
<br />
=== Windows 7 ===<br />
# Open "Devices and Printers" by clicking the Start button and then, on the Start menu, clicking "Devices and Printers".<br />
# Click Add a printer.<br />
# In the "Add Printer" wizard, click "Add a network, wireless or Bluetooth printer". <br />
# Windows will search for available printers, but you want to click "The printer that I want isn't listed".<br />
[[File:printer_isnt_listed.PNG|thumb<br />
|The printer that I want isn't listed]]<br />
# Select "Select a shared printer by name" and type <code>\\samba-itp\PRINTERNAME</code> while PRINTERNAME stands for the name of the printer e.g. "psKyo2".<br />
# If prompted, install the printer driver on your computer by clicking "Install driver". <br />
# Complete the additional steps in the wizard, and then click "Finish".<br />
<br />
=== Windows 10 ===<br />
Coming Soon!</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Baloo_file_indexing&diff=692Baloo file indexing2016-12-14T14:01:00Z<p>Thomas: Created page with "Baloo is a file indexing service and KDE Plasma Workspace will not work without it. In some cases indexing is makeing problem and consumming the whole system resourses. To cke..."</p>
<hr />
<div>Baloo is a file indexing service and KDE Plasma Workspace will not work without it. In some cases indexing is makeing problem and consumming the whole system resourses. To ckeck the system load run 'top' in a terminal. If you find a baloo process at the top of the list you may send it a kill signal. Type 'k' in the top program.<br />
<br />
You can disable indexing with the command:<br />
<br />
balooctl disable<br />
<br />
The command<br />
<br />
balooctl status<br />
<br />
will show you the current status.<br />
<br />
Unfortunatly there is no way to provide system defaults.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Main_Page&diff=691Main Page2016-12-14T13:54:40Z<p>Thomas: </p>
<hr />
<div>{| style="background:#f5faff;color:black" width="100%" align="center" cellpadding="5" cellspacing="2"<br />
|-<br />
| colspan=2 align=center style="background:#cef2e0" | '''Welcome to the ITP IT-Service Wiki'''<br />
|-<br />
| <br />
| <br />
|}<br />
<br />
In this Wiki you find information and documentation about our computer environment. Feel free to correct mistakes and add new content.<br />
<br />
Please read first: '''[[FAQ|Frequently asked questions]]''' and '''[http://th.physik.uni-frankfurt.de/cgi-bin/motd/generate.cgi Message of the day]''' <br />
<br />
'''For getting additional Support and reporting problems write to: [mailto:trouble@th.physik.uni-frankfurt.de trouble@th.physik.uni-frankfurt.de]'''<br />
<br />
'''New User Welcome Sheet''': [http://th.physik.uni-frankfurt.de/~thw/welcome-itp.pdf pdf]<br />
<br />
* [[General Information]] (includes Mail Setup)<br />
<br />
* New! [[Owncloud]] as Dropbox alternative<br />
<br />
* [[SAMBA Service]]<br />
<br />
* [[VPN Access]] or [[VPN with Networkmanager]]<br />
<br />
* [[Printing]]<br />
<br />
* [[Scanning with Brother MFC]]<br />
<br />
* [[X2GO| Graphical remote access with X2GO]]<br />
<br />
* [[mailfilter-setup]] to configure <br />
** [[vacman|Vacation]] aka "out of office reply"<br />
** [[Spam Filter]]<br />
** mail forwarding<br />
<br />
* [[SLURM]] - The next generation batch system<br />
<br />
* [[Storage and Backup]]<br />
<br />
* [[Archiving Data]]<br />
<br />
* [[Commercial Software]]<br />
<br />
* [[Intel Compiler]] New: Updated to Version 2017!<br />
<br />
* [[How to read scientific papers from home]]<br />
<br />
* [[Compiling and running MPI programs]]<br />
<br />
* [[Wien2k]]<br />
<br />
* [[Windows]]<br />
<br />
* [[TYPO3]]<br />
<br />
* [https://th.physik.uni-frankfurt.de/mailman/listinfo Mailing Listen]<br />
<br />
* [https://th.physik.uni-frankfurt.de/webmail Web Mail]<br />
<br />
=== Browser ===<br />
<br />
* [[Firefox: Annoying reset request]]<br />
<br />
=== KDE Problems and Hints === <br />
<br />
* [[Baloo file indexing]]<br />
<br />
<br />
== Getting started editing the Wiki ==<br />
<br />
*[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] <br />
*[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] <br />
*[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=690Intel Compiler2016-12-05T13:53:55Z<p>Thomas: /* Parts of the license */</p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
# old path Version 2013: ifortvars=/opt/intel/composer_xe_2013_sp1.2.144/bin/compilervars.sh<br />
<br />
ifortvar=/opt/intel/compilers_and_libraries_2017.0.098/linux/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== Parts of the license ==<br />
<br />
We own a license for "Intel® Parallel Studio XE Composer Edition for Fortran and C++ Linux" which includes the following components:<br />
<br />
* Intel® Parallel Studio XE Composer Edition for Fortran and C++ Linux<br />
* Intel® Data Analytics Acceleration Library for Linux<br />
* Intel® Distribution for Python for Linux<br />
* Intel® HD Graphics Drivers for Linux<br />
* Intel® Integrated Performance Primitives for Linux<br />
* Intel® Math Kernel Library for Linux<br />
* Intel® Parallel Studio XE Composer Edition for C++ Linux<br />
* Intel® Parallel Studio XE Composer Edition for Fortran Linux<br />
* Intel® Threading Building Blocks for Linux<br />
* Intel® Xeon Phi™ processor software Linux<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=689Intel Compiler2016-12-05T13:53:32Z<p>Thomas: </p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
# old path Version 2013: ifortvars=/opt/intel/composer_xe_2013_sp1.2.144/bin/compilervars.sh<br />
<br />
ifortvar=/opt/intel/compilers_and_libraries_2017.0.098/linux/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== Parts of the license ==<br />
<br />
We own a license for "Intel® Parallel Studio XE Composer Edition for Fortran and C++ Linux" which includes the following components:<br />
<br />
Intel® Parallel Studio XE Composer Edition for Fortran and C++ Linux<br />
Intel® Data Analytics Acceleration Library for Linux<br />
Intel® Distribution for Python for Linux<br />
Intel® HD Graphics Drivers for Linux<br />
Intel® Integrated Performance Primitives for Linux<br />
Intel® Math Kernel Library for Linux<br />
Intel® Parallel Studio XE Composer Edition for C++ Linux<br />
Intel® Parallel Studio XE Composer Edition for Fortran Linux<br />
Intel® Threading Building Blocks for Linux<br />
Intel® Xeon Phi™ processor software Linux<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=688Intel Compiler2016-11-09T15:53:52Z<p>Thomas: </p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
# old path Version 2013: ifortvars=/opt/intel/composer_xe_2013_sp1.2.144/bin/compilervars.sh<br />
<br />
ifortvar=/opt/intel/compilers_and_libraries_2017.0.098/linux/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== 32/64 bit Issues ==<br />
<br />
'''32 bit support is obsolete, we only have 64 bit machines.'''<br />
<br />
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine things can get more complicated. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and, less important, the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.<br />
<br />
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=687Intel Compiler2016-11-09T15:53:32Z<p>Thomas: </p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
# old path Version 2013: ifortvars=/opt/intel/composer_xe_2013_sp1.2.144/bin/compilervars.sh<br />
<br />
ifortvar=/opt/intel/compilers_and_libraries_2017.0.098/linux/bin$ compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== 32/64 bit Issues ==<br />
<br />
'''32 bit support is obsolete, we only have 64 bit machines.'''<br />
<br />
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine things can get more complicated. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and, less important, the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.<br />
<br />
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Main_Page&diff=686Main Page2016-11-09T15:51:13Z<p>Thomas: </p>
<hr />
<div>{| style="background:#f5faff;color:black" width="100%" align="center" cellpadding="5" cellspacing="2"<br />
|-<br />
| colspan=2 align=center style="background:#cef2e0" | '''Welcome to the ITP IT-Service Wiki'''<br />
|-<br />
| <br />
| <br />
|}<br />
<br />
In this Wiki you find information and documentation about our computer environment. Feel free to correct mistakes and add new content.<br />
<br />
Please read first: '''[[FAQ|Frequently asked questions]]''' and '''[http://th.physik.uni-frankfurt.de/cgi-bin/motd/generate.cgi Message of the day]''' <br />
<br />
'''For getting additional Support and reporting problems write to: [mailto:trouble@th.physik.uni-frankfurt.de trouble@th.physik.uni-frankfurt.de]'''<br />
<br />
'''New User Welcome Sheet''': [http://th.physik.uni-frankfurt.de/~thw/welcome-itp.pdf pdf]<br />
<br />
* [[General Information]] (includes Mail Setup)<br />
<br />
* New! [[Owncloud]] as Dropbox alternative<br />
<br />
* [[SAMBA Service]]<br />
<br />
* [[VPN Access]] or [[VPN with Networkmanager]]<br />
<br />
* [[Printing]]<br />
<br />
* [[Scanning with Brother MFC]]<br />
<br />
* [[X2GO| Graphical remote access with X2GO]]<br />
<br />
* [[mailfilter-setup]] to configure <br />
** [[vacman|Vacation]] aka "out of office reply"<br />
** [[Spam Filter]]<br />
** mail forwarding<br />
<br />
* [[SLURM]] - The next generation batch system<br />
<br />
* [[Storage and Backup]]<br />
<br />
* [[Archiving Data]]<br />
<br />
* [[Commercial Software]]<br />
<br />
* [[Intel Compiler]] New: Updated to Version 2017!<br />
<br />
* [[How to read scientific papers from home]]<br />
<br />
* [[Compiling and running MPI programs]]<br />
<br />
* [[Wien2k]]<br />
<br />
* [[Windows]]<br />
<br />
* [[TYPO3]]<br />
<br />
* [https://th.physik.uni-frankfurt.de/mailman/listinfo Mailing Listen]<br />
<br />
* [https://th.physik.uni-frankfurt.de/webmail Web Mail]<br />
<br />
=== Browser ===<br />
<br />
* [[Firefox: Annoying reset request]]<br />
<br />
=== Mac Client Support ===<br />
<br />
* [[Enable cups browsing]]<br />
<br />
<br />
== Getting started editing the Wiki ==<br />
<br />
*[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] <br />
*[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] <br />
*[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Main_Page&diff=685Main Page2016-11-09T15:50:16Z<p>Thomas: </p>
<hr />
<div>{| style="background:#f5faff;color:black" width="100%" align="center" cellpadding="5" cellspacing="2"<br />
|-<br />
| colspan=2 align=center style="background:#cef2e0" | '''Welcome to the ITP IT-Service Wiki'''<br />
|-<br />
| <br />
| <br />
|}<br />
<br />
In this Wiki you find information and documentation about our computer environment. Feel free to correct mistakes and add new content.<br />
<br />
Please read first: '''[[FAQ|Frequently asked questions]]''' and '''[http://th.physik.uni-frankfurt.de/cgi-bin/motd/generate.cgi Message of the day]''' <br />
<br />
'''For getting additional Support and reporting problems write to: [mailto:trouble@th.physik.uni-frankfurt.de trouble@th.physik.uni-frankfurt.de]'''<br />
<br />
'''New User Welcome Sheet''': [http://th.physik.uni-frankfurt.de/~thw/welcome-itp.pdf pdf]<br />
<br />
* [[General Information]] (includes Mail Setup)<br />
<br />
* New! [[Owncloud]] as Dropbox alternative<br />
<br />
* [[SAMBA Service]]<br />
<br />
* [[VPN Access]] or [[VPN with Networkmanager]]<br />
<br />
* [[Printing]]<br />
<br />
* [[Scanning with Brother MFC]]<br />
<br />
* [[X2GO| Graphical remote access with X2GO]]<br />
<br />
* [[mailfilter-setup]] to configure <br />
** [[vacman|Vacation]] aka "out of office reply"<br />
** [[Spam Filter]]<br />
** mail forwarding<br />
<br />
* [[SLURM]] - The next generation batch system<br />
<br />
* [[Storage and Backup]]<br />
<br />
* [[Archiving Data]]<br />
<br />
* [[Commercial Software]]<br />
<br />
* [[Inter Compiler]] New: Updated to Version 2017!<br />
<br />
* [[How to read scientific papers from home]]<br />
<br />
* [[Compiling and running MPI programs]]<br />
<br />
* [[Wien2k]]<br />
<br />
* [[Windows]]<br />
<br />
* [[TYPO3]]<br />
<br />
* [https://th.physik.uni-frankfurt.de/mailman/listinfo Mailing Listen]<br />
<br />
* [https://th.physik.uni-frankfurt.de/webmail Web Mail]<br />
<br />
=== Browser ===<br />
<br />
* [[Firefox: Annoying reset request]]<br />
<br />
=== Mac Client Support ===<br />
<br />
* [[Enable cups browsing]]<br />
<br />
<br />
== Getting started editing the Wiki ==<br />
<br />
*[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] <br />
*[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] <br />
*[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Commercial_Software&diff=684Commercial Software2016-10-14T13:01:24Z<p>Thomas: /* NAG Libraries */</p>
<hr />
<div>We have several Commercial Software Package installed on our System. This document describes what we have and how to use them.<br />
<br />
= Mathematica =<br />
<br />
Mathematica is an algebra system from Wolfram Research [http://www.wolfram.com/]. Currenly we provide version 9.0.<br />
<br />
Because mathematica is very expensive we only hold a limited number of licenses. For fairness to other users, please close Mathematica if you don't need it. If everyone will do this, you will have not to wait for a license token.<br />
<br />
== Remote usage of Mathematica ==<br />
<br />
If you want to use Mathematica through a ssh-connection or through our [[nxserver|NX-Server]], the Mathematica fonts have to be installed on your local machine.<br />
<br />
The recent Ubuntu 10.04 has a new package which can do this for you. Open your favorite software managment tool (eg. synaptic) or open a terminal window and enter:<br />
<br />
sudo aptitude install mathematica-fonts<br />
<br />
This is a downloader package and downloads the fonts from the Mathematica site. <br />
<br />
For older Ubuntu and Debian Versions we provide special packages. This packages can only be downloaded if your are at the ITP. Download the following files:<br />
<br />
http://th.physik.uni-frankfurt.de/~xela/ubuntu/pool/non-free/mathematica-xfonts-type1_5.2.0.0-1.13b_all.deb<br />
http://th.physik.uni-frankfurt.de/~xela/ubuntu/pool/non-free/mathematica-xfonts-75dpi_5.2.0.0-1.13b_i386.deb<br />
http://th.physik.uni-frankfurt.de/~xela/ubuntu/pool/non-free/mathematica-xfonts-75dpi_5.2.0.0-1.13b_amd64.deb<br />
<br />
and install them with the command:<br />
<br />
sudo dpkg -i *.deb<br />
<br />
= Maple =<br />
<br />
Maple 12 is available with either "xmaple" or "maple".<br />
<br />
= Matlab =<br />
<br />
Matlab is available in a recent version with the command "matlab".<br />
<br />
There is a issue with the java virtual memory, when running matlab on the login server. The Java GUI will only run on our normal desktop machines.<br />
<br />
= Intel Compiler and MKL =<br />
<br />
See [[Intel Compiler]] for details instructions, how to setup your environment.<br />
<br />
= NAG Libraries =<br />
<br />
The NAG libraries are installed under /home/software/NAG, accessible from all ITP machines.<br />
<br />
Currenly we have:<br />
* cll6i24dcl (C Version, 64 bit integer)<br />
* fll6a24dfl (Fortran Version)<br />
<br />
The Libraries are not in the default library path. If you want the use them you have to set or extend the LD_LIBRARY_PATH. Run your programm like that<br />
<br />
LD_LIBRARY_PATH=/home/software/NAG/cll6i24dcl/lib ./a.out<br />
<br />
if your binary is named a.out. You can put the LD_LIBRARY_PATH with an export statement in your .profile to have it always available.<br />
<br />
The NAG Libraries are commercial software and require a valid license. Define a second environment variable pointing to the license file:<br />
<br />
export NAG_KUSARI_FILE=/home/software/NAG/license.lic<br />
<br />
This can also be added to the .profile.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SLURM&diff=680SLURM2016-08-25T09:55:11Z<p>Thomas: </p>
<hr />
<div>SLURM is the Simple Linux Utility for Resource Management and is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.<br />
<br />
Slurm is fully integrated in our system. You do not need set any environment variables.<br />
<br />
<br />
== Partitions ==<br />
<br />
A partition is a subset of the cluster, a bundle of compute nodes with the same characteristics.<br />
<br />
Based on access restrictions our cluster is divided in different partitions. 'sinfo' will only show partitions you are allowed to use. Using 'sinfo -a' shows all partitons.<br />
<br />
A partition is selected by '-p PARTITIONNAME'.<br />
<br />
{| border="1" align="center"<br />
|-<br />
! scope="col" | '''Partition''' <br />
! scope="col" | '''No. Nodes''' <br />
! scope="col" | '''Cores''' <br />
! scope="col" | '''Tot. Cores'''<br />
! scope="col" | '''RAM/GB''' <br />
! scope="col" | '''CPU''' <br />
! scope="col" | '''Remark'''<br />
|-<br />
| itp <br />
| 10<br />
| 12 <br />
| 120<br />
| 32 <br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
|-<br />
| dfg <br />
| 9<br />
| 8 <br />
| 72<br />
| 32 <br />
| Quad-Core AMD Opteron(tm) Processor 2346 HE <br />
| '''mostly out of service'''<br />
|-<br />
| dfg<br />
| 8<br />
| 8<br />
| 64<br />
| 32/64<br />
| Quad-Core AMD Opteron(tm) Processor 2376 <br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| dfg<br />
| 8 <br />
| 12<br />
| 96<br />
| 32/64<br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| quantum<br />
| 8<br />
| 12<br />
| 96<br />
| 32/64<br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 32<br />
| 96<br />
| 128<br />
| 8-Core AMD Opteron(tm) Processor 6128<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 48<br />
| 144<br />
| 128/256<br />
| 12-Core AMD Opteron(tm) Processor 6168<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 4<br />
| 64<br />
| 256<br />
| 128/256<br />
| 16-Core AMD Opteron(tm) Processor 6272<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 4<br />
| 48<br />
| 192<br />
| 128/256<br />
| 12-Core AMD Opteron(tm) Processor 6344<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 24<br />
| 72<br />
| 64<br />
| 12-Core AMD Opteron(tm) Processor 6344<br />
| '''Restricted access'''<br />
|-<br />
| fplo<br />
| 2<br />
| 12<br />
| 24<br />
| 256<br />
| Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz<br />
| '''Restricted access'''<br />
|-<br />
| fplo<br />
| 2<br />
| 16<br />
| 32<br />
| 256<br />
| Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz<br />
| '''Restricted access'''<br />
|-<br />
| dfg-xeon<br />
| 8<br />
| 16<br />
| 128<br />
| 64/128<br />
| Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz<br />
| '''Restricted access'''<br />
<br />
|}<br />
<br />
The access to the DFG-Nodes (dfg and dfg-big) is restricted to the members of the SFB/TR49. If you do not belong to that group but want to test and develop programs for the Infiniband Network, please talk to the administrator. The queue 'fplo' have the same restrictions like the dfg-queue and is intended for large memory and single threaded job from the program 'fplo'.<br />
The access to the queue 'quantum' is restricted to group Prof. Hofstetter.<br />
<br />
== Submitting Jobs ==<br />
<br />
In most case you want to submit a non interactive job to be executed in our cluster.<br />
<br />
This is very simple for serial (1 CPU) jobs:<br />
<br />
sbatch -p PARTITION jobscript.sh<br />
<br />
where jobscript.sh is a shell script with your job commands.<br />
<br />
Running '''openMPI''' jobs is not much more complictated:<br />
<br />
sbatch -p PARTITION -n X jobscript.sh<br />
<br />
where X is the number of desired MPI processes. Launch the job in the jobscript with:<br />
<br />
mpirun YOUREXECUTABLE<br />
<br />
You don't have to worry about the number of processes or specific nodes. Both slurm and openmpi know<br />
about each other.<br />
<br />
If you want '''infiniband''' for your MPI job (which is usually a good idea, if not running on the same node), you have to request the feature infiniband:<br />
<br />
sbatch -p dfg -C infiniband -n X jobscript.sh<br />
<br />
Note: Infiniband is only available for the partitions dfg and quantum.<br />
<br />
Running '''SMP jobs''' (multiple threads, not necessary mpi). Running MPI jobs an a single node, is recommended for the<br />
dfg-big nodes. This are big host, with up to 64 cpu's per node, but 'slow' gigabit network connection. Launch SMP jobs with<br />
<br />
sbatch -p PARTITION -N 1 -n X jobscript.sh<br />
<br />
=== Differences in network the network connection ===<br />
<br />
The new v3 dfg-xeon nodes are equipped with 10 GB network. This is faster (trough put) and has lower latency then gigabit ethernet, but is not is not as fast as the DDR infinband network. The 10 GB network is used for MPI and I/O. Infiniband is only use for MPI.<br />
<br />
== Defining Resource limits ==<br />
<br />
By default each job allocates 2 GB memory and a run time of 3 days. More resources can be requested by<br />
<br />
--mem-per-cpu=<MB><br />
<br />
where <MB> is the memory in megabytes. The virtual memory limit is 2.5 times of the requested real memory limit.<br />
<br />
The memory limit is not a hard limit. When exceeding the limit, your memory will be swapped out. Only when using more the 150% of the limit your job will be killed. So be conservative, to keep enough room for other jobs. Requested memory is blocked from the use by other jobs.<br />
<br />
-t or --time=<time><br />
<br />
where time can by "days-hours". See man page for more formats.<br />
<br />
<br />
== Memory Management ==<br />
<br />
In Slurm you specify only one parameter, which is the limit for your real memory usage and drives the decision where your job is started. The virtual memory of your job maybe 2.5 times of your requested memory. You can exceed you memory limit by 50%. But this will be swap space instead of real memory. This prevents crashing if you memory limit is a little to tight.<br />
<br />
== Inline Arguments ==<br />
<br />
sbatch arguments can be written in the jobfile:<br />
<br />
<pre><br />
#! /bin/bash<br />
#<br />
# Choosing a partition:<br />
#SBATCH -p housewives<br />
<br />
YOUR JOB COMMANDS....<br />
</pre><br />
<br />
= Links =<br />
<br />
* SLURM-Homepage [http://slurm.schedmd.com/slurm.html]</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=679Owncloud2016-03-11T15:06:01Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need the have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options we recommend:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After login to the Owncloud server, you will find some example files and (important) the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write to the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=678Owncloud2016-03-11T10:05:51Z<p>Thomas: /* Additional Help */</p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need the have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options we recommend:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After login to the Owncloud server, you will find some example files and (important) the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write to the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=677Owncloud2016-03-11T09:40:46Z<p>Thomas: /* Where to store you synced data on the ITP computer */</p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need the have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options we recommend:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After logging to the Owncloud server, you will find some example files and the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=676Owncloud2016-03-11T09:40:12Z<p>Thomas: /* Where to store you synced data */</p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data on the ITP computer ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After logging to the Owncloud server, you will find some example files and the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=675Owncloud2016-03-11T09:39:36Z<p>Thomas: /* Additional Help */</p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After logging to the Owncloud server, you will find some example files and the Owncloud User Manual. Please read this first to understand how to use the system. If there are still questions, you may write the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=674Owncloud2016-03-11T09:39:04Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.<br />
<br />
== Additional Help ==<br />
<br />
After loggin to the owncloud server, you will find some example files and the Owncloud User Manual. Please read this first, to understand how to use the system. If there are still questions, you may write the usual support address.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=673Owncloud2016-03-11T09:36:21Z<p>Thomas: /* Where to store you synced data */</p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' and but it there. This is in the exclude list from the daily backup.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=672Owncloud2016-03-11T09:35:46Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
== Where to store you synced data ==<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' und but it there. This is in the exclude list from the daily backup.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=671Owncloud2016-03-11T09:35:22Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
Where to store you synced data<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
# If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
# In your home create a sub directory 'nobackup' und but it there. This is in the exclude list from the daily backup.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=670Owncloud2016-03-11T09:34:42Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].<br />
<br />
[[Where to store you synced data]]<br />
<br />
The Owncloud Server has its own backup and an internal undo function. So there is basically no need have an additional backup from the home directory. If you only have some hundreds of mega bytes, don't worry. For larger file sets there are two options:<br />
<br />
1. If your computer has a /data partition, put it there. But it's only accessible from the computer itself.<br />
<br />
2. In your home create a sub directory 'nobackup' und but it there. This is in the exclude list from the daily backup.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=669Owncloud2016-03-11T09:26:22Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is https://cloud.itp.uni-frankfurt.de.<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=668Owncloud2016-03-11T09:25:07Z<p>Thomas: </p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is [https://cloud.itp.uni-frankfurt.de|https://cloud.itp.uni-frankfurt.de].<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Owncloud&diff=667Owncloud2016-03-11T09:24:30Z<p>Thomas: Created page with "Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere..."</p>
<hr />
<div>Owncloud is a platform for storing, syncing and sharing files. It is mainly targeted as alternative to Dropbox. Dropbox is highly political because the data is store somewhere in the world esp. USA, with data protection rules not compatible with ours. The Owcloud is hosted in our server room.<br />
<br />
The address is [https://cloud.itp.uni-frankfurt.de].<br />
<br />
The login is your normal ITP login. But this is already using the upcoming LDAP service. If you changed your password within the last year, the password my be wrong. If you don't remember your old password, please send a note to trouble@th.physik.uni-frankfurt.de. We will copy your recent (hashed) password to the LDAP. Don't (Never!) expose any password details.<br />
<br />
On our Linux installation the the sync client is already installed. Search for "Owncloud desktop sync client", from the command line start "owncloud". The installation is self explaining. Use the server address from above.<br />
<br />
For other operating systems the clients are offered for download from the first login, or from the owncloud website [http://owncloud.org].</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Main_Page&diff=666Main Page2016-03-11T08:45:45Z<p>Thomas: </p>
<hr />
<div>{| style="background:#f5faff;color:black" width="100%" align="center" cellpadding="5" cellspacing="2"<br />
|-<br />
| colspan=2 align=center style="background:#cef2e0" | '''Welcome to the ITP IT-Service Wiki'''<br />
|-<br />
| <br />
| <br />
|}<br />
<br />
In this Wiki you find information and documentation about our computer environment. Feel free to correct mistakes and add new content.<br />
<br />
Please read first: '''[[FAQ|Frequently asked questions]]''' and '''[http://th.physik.uni-frankfurt.de/cgi-bin/motd/generate.cgi Message of the day]''' <br />
<br />
'''For getting additional Support and reporting problems write to: [mailto:trouble@th.physik.uni-frankfurt.de trouble@th.physik.uni-frankfurt.de]'''<br />
<br />
'''New User Welcome Sheet''': [http://th.physik.uni-frankfurt.de/~thw/welcome-itp.pdf pdf]<br />
<br />
* [[General Information]] (includes Mail Setup)<br />
<br />
* New! [[Owncloud]] as Dropbox alternative<br />
<br />
* [[SAMBA Service]]<br />
<br />
* [[VPN Access]] or [[VPN with Networkmanager]]<br />
<br />
* [[Printing]]<br />
<br />
* [[Scanning with Brother MFC]]<br />
<br />
* [[X2GO| Graphical remote access with X2GO]]<br />
<br />
* [[mailfilter-setup]] to configure <br />
** [[vacman|Vacation]] aka "out of office reply"<br />
** [[Spam Filter]]<br />
** mail forwarding<br />
<br />
* [[SLURM]] - The next generation batch system<br />
<br />
* [[Storage and Backup]]<br />
<br />
* [[Archiving Data]]<br />
<br />
* [[Commercial Software]]<br />
<br />
* [[How to read scientific papers from home]]<br />
<br />
* [[Compiling and running MPI programs]]<br />
<br />
* [[Wien2k]]<br />
<br />
* [[Windows]]<br />
<br />
* [[TYPO3]]<br />
<br />
* [https://th.physik.uni-frankfurt.de/mailman/listinfo Mailing Listen]<br />
<br />
* [https://th.physik.uni-frankfurt.de/webmail Web Mail]<br />
<br />
=== Browser ===<br />
<br />
* [[Firefox: Annoying reset request]]<br />
<br />
=== Mac Client Support ===<br />
<br />
* [[Enable cups browsing]]<br />
<br />
<br />
== Getting started editing the Wiki ==<br />
<br />
*[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] <br />
*[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] <br />
*[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=665Intel Compiler2016-03-08T09:50:50Z<p>Thomas: /* .bashrc */</p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
# old path: ifortvars=/opt/intel/bin/compilervars.sh<br />
ifortvars=/opt/intel/composer_xe_2013_sp1.2.144/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== 32/64 bit Issues ==<br />
<br />
'''32 bit support is obsolete, we only have 64 bit machines.'''<br />
<br />
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine things can get more complicated. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and, less important, the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.<br />
<br />
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Main_Page&diff=664Main Page2016-02-19T13:50:21Z<p>Thomas: </p>
<hr />
<div>{| style="background:#f5faff;color:black" width="100%" align="center" cellpadding="5" cellspacing="2"<br />
|-<br />
| colspan=2 align=center style="background:#cef2e0" | '''Welcome to the ITP IT-Service Wiki'''<br />
|-<br />
| <br />
| <br />
|}<br />
<br />
In this Wiki you find information and documentation about our computer environment. Feel free to correct mistakes and add new content.<br />
<br />
Please read first: '''[[FAQ|Frequently asked questions]]''' and '''[http://th.physik.uni-frankfurt.de/cgi-bin/motd/generate.cgi Message of the day]''' <br />
<br />
'''For getting additional Support and reporting problems write to: [mailto:trouble@th.physik.uni-frankfurt.de trouble@th.physik.uni-frankfurt.de]'''<br />
<br />
'''New User Welcome Sheet''': [http://th.physik.uni-frankfurt.de/~thw/welcome-itp.pdf pdf]<br />
<br />
* [[General Information]] (includes Mail Setup)<br />
<br />
* [[SAMBA Service]]<br />
<br />
* [[VPN Access]] or [[VPN with Networkmanager]]<br />
<br />
* [[Printing]]<br />
<br />
* [[Scanning with Brother MFC]]<br />
<br />
* [[X2GO| Graphical remote access with X2GO]]<br />
<br />
* [[mailfilter-setup]] to configure <br />
** [[vacman|Vacation]] aka "out of office reply"<br />
** [[Spam Filter]]<br />
** mail forwarding<br />
<br />
* [[SLURM]] - The next generation batch system<br />
<br />
* [[Storage and Backup]]<br />
<br />
* [[Archiving Data]]<br />
<br />
* [[Commercial Software]]<br />
<br />
* [[How to read scientific papers from home]]<br />
<br />
* [[Compiling and running MPI programs]]<br />
<br />
* [[Wien2k]]<br />
<br />
* [[Windows]]<br />
<br />
* [[TYPO3]]<br />
<br />
* [https://th.physik.uni-frankfurt.de/mailman/listinfo Mailing Listen]<br />
<br />
* [https://th.physik.uni-frankfurt.de/webmail Web Mail]<br />
<br />
=== Browser ===<br />
<br />
* [[Firefox: Annoying reset request]]<br />
<br />
=== Mac Client Support ===<br />
<br />
* [[Enable cups browsing]]<br />
<br />
<br />
== Getting started editing the Wiki ==<br />
<br />
*[http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] <br />
*[http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] <br />
*[http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
<br />
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=663Intel Compiler2016-02-19T13:44:04Z<p>Thomas: /* Implicit parallelization */</p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
ifortvars=/opt/intel/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== 32/64 bit Issues ==<br />
<br />
'''32 bit support is obsolete, we only have 64 bit machines.'''<br />
<br />
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine things can get more complicated. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and, less important, the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.<br />
<br />
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=662Intel Compiler2016-02-19T13:42:46Z<p>Thomas: /* 32/64 bit Issues */</p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
ifortvars=/opt/intel/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== 32/64 bit Issues ==<br />
<br />
'''32 bit support is obsolete, we only have 64 bit machines.'''<br />
<br />
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine things can get more complicated. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and, less important, the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.<br />
<br />
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value. In the SGE the have to use the PE 'smp' to ensure all parallel slots are located on the same machine.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Intel_Compiler&diff=661Intel Compiler2016-02-19T13:41:23Z<p>Thomas: </p>
<hr />
<div>This page describes, how to setup your environment for using our Intel Compiler Installation. The instruction are for '''bash''' shell user. If you use a different shell, you know what you are doing and you will be able to translate the configuration. <br />
<br />
We provide the recent version 13 of the Intel compiler suite for Fortran, C/C++ and the full set of performance libraries like MKL, TBB, Cluster_OMP.<br />
<br />
== .bashrc ==<br />
<br />
In order to use the installation you have to modify your '''.bashrc'''. Open the file with you favorite editor and append the following lines.<br />
<br />
<pre><br />
#Intel Compiler Setup<br />
export LM_LICENSE_FILE="16287@th.physik.uni-frankfurt.de"<br />
<br />
intel_arch="intel64"<br />
<br />
ifortvars=/opt/intel/bin/compilervars.sh<br />
if [ -f $ifortvars ]; then<br />
. $ifortvars $intel_arch<br />
fi<br />
<br />
</pre><br />
<br />
There are similar files with .csh extension for C-Shell users.<br />
<br />
After sourcing your .bashrc or opening an new shell you can validate your setup with 'which ifort'. This should point to somewhere in /opt.<br />
<br />
== 32/64 bit Issues ==<br />
<br />
If you only work on 64 bit machines you can skip this section. But if you are working on 32 bit machine things can get more complicated. If you exclusively work on a 32 bit and you don't want the run your programs on the our HPC nodes you can also skip this. 32 bit machines are mainly the white FSC boxes and, less important, the pool. Running "uname -m" in a shell will tell you your architecture: i686 for 32 or x86_64 for 64 bit. The setup above will choose the appropriate environment.<br />
<br />
If you are using a 32bit machine and want use the HPC nodes, it is recommended that you login to our login server th.physik.uni-frankfurt.de an compile your code there. 32 bit programs will run on 64 bit but have some limitations. A small performance impact and limited address space (4 GB) with much less usable ram.<br />
<br />
== Implicit parallelization ==<br />
<br />
This version of MKL has internal parallel code (based on openMP) which uses all CPUs in the system. This is fine on the desktop as it will speed up your caluclation. But on the compute nodes this will conflict with other jobs running on the same machine. Therefore you have to restrict the number CPUs used to the number of allocated slots in SGE. Your can do this by defining the following environment variable:<br />
<br />
export OMP_NUM_THREADS=x<br />
<br />
where x is the number of allocated slots. Using 1 means traditional serial processing. You should benchmark your program how many parallel threads will give a reasonable performance per CPU value. In the SGE the have to use the PE 'smp' to ensure all parallel slots are located on the same machine.<br />
<br />
== Documentation ==<br />
<br />
The comprehensive set of Intel documentation will be found under '''/opt/intel/composerxe/Documentation/en_US'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SAMBA_Service&diff=660SAMBA Service2016-02-04T16:07:53Z<p>Thomas: </p>
<hr />
<div>We've set up a whole new Samba service for you which is fully integrated into upcoming LDAP service for authentication. If you have changed your password recently, the passwords may not match. Send a mail to trouble for a resync. <br />
<br />
=== Windows 7 ===<br />
# Open Computer by clicking the Start button and then clicking "Computer".<br />
# Click "Map network drive".<br />
[[File:Win7_computer.PNG|thumb<br />
|Map network drive in Computer (Windows 7)]]<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at logon" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification. <br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
=== Windows 10 ===<br />
# Open File Explorer and on the left select "This PC".<br />
# Click the "Map network drive" button in the ribbon menu at the top. <br />
[[File:Win10_this_pc.PNG|thumb<br />
|Map network drive in This PC (Windows 10)]]<br />
# Then select "Map network drive." This is under the "Computer" tab, which should open automatically when you go to This PC, as above.<br />
# In the "Drive" list, click a drive letter. You can choose any available letter.<br />
# In the "Folder" box, type <code>\\samba-itp\USERNAME</code> while USERNAME stands for your own login name. To connect every time you log on to your computer, select the "Reconnect at sign-in" check box.<br />
# Click "Finish". You will be ask to type in your login name and passwort for verification.<br />
# Click "OK". Your computer is now connected, or mapped, to the network drive.<br />
<br />
== Connect to SAMBA printers ==<br />
<br />
Connecting to printers work as above.<br />
<br />
=== Windows 7 ===<br />
# Open "Devices and Printers" by clicking the Start button and then, on the Start menu, clicking "Devices and Printers".<br />
# Click Add a printer.<br />
# In the "Add Printer" wizard, click "Add a network, wireless or Bluetooth printer". <br />
# Windows will search for available printers, but you want to click "The printer that I want isn't listed".<br />
[[File:printer_isnt_listed.PNG|thumb<br />
|The printer that I want isn't listed]]<br />
# Select "Select a shared printer by name" and type <code>\\samba-itp\PRINTERNAME</code> while PRINTERNAME stands for the name of the printer e.g. "psKyo2".<br />
# If prompted, install the printer driver on your computer by clicking "Install driver". <br />
# Complete the additional steps in the wizard, and then click "Finish".<br />
<br />
=== Windows 10 ===<br />
Coming Soon!</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SLURM&diff=654SLURM2016-01-26T08:25:21Z<p>Thomas: </p>
<hr />
<div>SLURM is the Simple Linux Utility for Resource Management and is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.<br />
<br />
Slurm is fully integrated in our system. You do not need set any environment variables.<br />
<br />
<br />
== Partitions ==<br />
<br />
A partition is a subset of the cluster, a bundle of compute nodes with the same characteristics.<br />
<br />
Based on access restrictions our cluster is divided in different partitions. 'sinfo' will only show partitions you are allowed to use. Using 'sinfo -a' shows all partitons.<br />
<br />
A partition is selected by '-p PARTITIONNAME'.<br />
<br />
{| border="1" align="center"<br />
|-<br />
! scope="col" | '''Partition''' <br />
! scope="col" | '''No. Nodes''' <br />
! scope="col" | '''Cores''' <br />
! scope="col" | '''Tot. Cores'''<br />
! scope="col" | '''RAM/GB''' <br />
! scope="col" | '''CPU''' <br />
! scope="col" | '''Remark'''<br />
|-<br />
| itp <br />
| 10<br />
| 12 <br />
| 120<br />
| 32 <br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
|-<br />
| dfg <br />
| 9<br />
| 8 <br />
| 72<br />
| 32 <br />
| Quad-Core AMD Opteron(tm) Processor 2346 HE <br />
| '''Restricted access'''<br />
|-<br />
| dfg<br />
| 8<br />
| 8<br />
| 64<br />
| 32/64<br />
| Quad-Core AMD Opteron(tm) Processor 2376 <br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| dfg<br />
| 8 <br />
| 12<br />
| 96<br />
| 32/64<br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| quantum<br />
| 8<br />
| 12<br />
| 96<br />
| 32/64<br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 32<br />
| 96<br />
| 128<br />
| 8-Core AMD Opteron(tm) Processor 6128<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 48<br />
| 144<br />
| 128/256<br />
| 12-Core AMD Opteron(tm) Processor 6168<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 4<br />
| 64<br />
| 256<br />
| 128/256<br />
| 16-Core AMD Opteron(tm) Processor 6272<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 4<br />
| 48<br />
| 192<br />
| 128/256<br />
| 12-Core AMD Opteron(tm) Processor 6344<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 24<br />
| 72<br />
| 64<br />
| 12-Core AMD Opteron(tm) Processor 6344<br />
| '''Restricted access'''<br />
|-<br />
| fplo<br />
| 2<br />
| 12<br />
| 24<br />
| 256<br />
| Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz<br />
| '''Restricted access'''<br />
|-<br />
| fplo<br />
| 2<br />
| 16<br />
| 32<br />
| 256<br />
| Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz<br />
| '''Restricted access'''<br />
|-<br />
| dfg-xeon<br />
| 8<br />
| 16<br />
| 128<br />
| 64/128<br />
| Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz<br />
| '''Restricted access'''<br />
<br />
|}<br />
<br />
The access to the DFG-Nodes (dfg and dfg-big) is restricted to the members of the SFB/TR49. If you do not belong to that group but want to test and develop programs for the Infiniband Network, please talk to the administrator. The queue 'fplo' have the same restrictions like the dfg-queue and is intended for large memory and single threaded job from the program 'fplo'.<br />
The access to the queue 'quantum' is restricted to group Prof. Hofstetter.<br />
<br />
== Submitting Jobs ==<br />
<br />
In most case you want to submit a non interactive job to be executed in our cluster.<br />
<br />
This is very simple for serial (1 CPU) jobs:<br />
<br />
sbatch -p PARTITION jobscript.sh<br />
<br />
where jobscript.sh is a shell script with your job commands.<br />
<br />
Running '''openMPI''' jobs is not much more complictated:<br />
<br />
sbatch -p PARTITION -n X jobscript.sh<br />
<br />
where X is the number of desired MPI processes. Launch the job in the jobscript with:<br />
<br />
mpirun YOUREXECUTABLE<br />
<br />
You don't have to worry about the number of processes or specific nodes. Both slurm and openmpi know<br />
about each other.<br />
<br />
If you want '''infiniband''' for your MPI job (which is usually a good idea, if not running on the same node), you have to request the feature infiniband:<br />
<br />
sbatch -p dfg -C infiniband -n X jobscript.sh<br />
<br />
Note: Infiniband is only available for the partitions dfg and quantum.<br />
<br />
Running '''SMP jobs''' (multiple threads, not necessary mpi). Running MPI jobs an a single node, is recommended for the<br />
dfg-big nodes. This are big host, with up to 64 cpu's per node, but 'slow' gigabit network connection. Launch SMP jobs with<br />
<br />
sbatch -p PARTITION -N 1 -n X jobscript.sh<br />
<br />
=== Differences in network the network connection ===<br />
<br />
The new v3 dfg-xeon nodes are equipped with 10 GB network. This is faster (trough put) and has lower latency then gigabit ethernet, but is not is not as fast as the DDR infinband network. The 10 GB network is used for MPI and I/O. Infiniband is only use for MPI.<br />
<br />
== Defining Resource limits ==<br />
<br />
By default each job allocates 2 GB memory and a run time of 3 days. More resources can be requested by<br />
<br />
--mem-per-cpu=<MB><br />
<br />
where <MB> is the memory in megabytes. The virtual memory limit is 2.5 times of the requested real memory limit.<br />
<br />
The memory limit is not a hard limit. When exceeding the limit, your memory will be swapped out. Only when using more the 150% of the limit your job will be killed. So be conservative, to keep enough room for other jobs. Requested memory is blocked from the use by other jobs.<br />
<br />
-t or --time=<time><br />
<br />
where time can by "days-hours". See man page for more formats.<br />
<br />
<br />
== Memory Management ==<br />
<br />
In Slurm you specify only one parameter, which is the limit for your real memory usage and drives the decision where your job is started. The virtual memory of your job maybe 2.5 times of your requested memory. You can exceed you memory limit by 50%. But this will be swap space instead of real memory. This prevents crashing if you memory limit is a little to tight.<br />
<br />
== Inline Arguments ==<br />
<br />
sbatch arguments can be written in the jobfile:<br />
<br />
<pre><br />
#! /bin/bash<br />
#<br />
# Choosing a partition:<br />
#SBATCH -p housewives<br />
<br />
YOUR JOB COMMANDS....<br />
</pre><br />
<br />
= Links =<br />
<br />
* SLURM-Homepage [http://slurm.schedmd.com/slurm.html]</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=SLURM&diff=638SLURM2015-12-17T12:30:35Z<p>Thomas: /* Partitions */</p>
<hr />
<div>SLURM is the Simple Linux Utility for Resource Management and is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.<br />
<br />
Slurm is fully integrated in our system. You do not need set any environment variables.<br />
<br />
<br />
== Partitions ==<br />
<br />
A partition is a subset of the cluster, a bundle of compute nodes with the same characteristics.<br />
<br />
Based on access restrictions our cluster is divided in different partitions. 'sinfo' will only show partitions you are allowed to use. Using 'sinfo -a' shows all partitons.<br />
<br />
A partition is selected by '-p PARTITIONNAME'.<br />
<br />
{| border="1" align="center"<br />
|-<br />
! scope="col" | '''Partition''' <br />
! scope="col" | '''No. Nodes''' <br />
! scope="col" | '''Cores''' <br />
! scope="col" | '''Tot. Cores'''<br />
! scope="col" | '''RAM/GB''' <br />
! scope="col" | '''CPU''' <br />
! scope="col" | '''Remark'''<br />
|-<br />
| itp <br />
| 10<br />
| 12 <br />
| 120<br />
| 32 <br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
|-<br />
| dfg <br />
| 9<br />
| 8 <br />
| 72<br />
| 32 <br />
| Quad-Core AMD Opteron(tm) Processor 2346 HE <br />
| '''Restricted access'''<br />
|-<br />
| dfg<br />
| 8<br />
| 8<br />
| 64<br />
| 32/64<br />
| Quad-Core AMD Opteron(tm) Processor 2376 <br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| dfg<br />
| 8 <br />
| 12<br />
| 96<br />
| 32/64<br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| quantum<br />
| 8<br />
| 12<br />
| 96<br />
| 32/64<br />
| Six-Core AMD Opteron(tm) Processor 2427<br />
| [http://en.wikipedia.org/wiki/InfiniBand Infiniband], '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 32<br />
| 96<br />
| 128<br />
| 8-Core AMD Opteron(tm) Processor 6128<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 48<br />
| 144<br />
| 128/256<br />
| 12-Core AMD Opteron(tm) Processor 6168<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 4<br />
| 64<br />
| 256<br />
| 128/256<br />
| 16-Core AMD Opteron(tm) Processor 6272<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 4<br />
| 48<br />
| 192<br />
| 128/256<br />
| 12-Core AMD Opteron(tm) Processor 6344<br />
| '''Restricted access'''<br />
|-<br />
| dfg-big<br />
| 3<br />
| 24<br />
| 72<br />
| 64<br />
| 12-Core AMD Opteron(tm) Processor 6344<br />
| '''Restricted access'''<br />
|-<br />
| fplo<br />
| 2<br />
| 12<br />
| 24<br />
| 256<br />
| Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz<br />
| '''Restricted access'''<br />
|-<br />
| fplo<br />
| 2<br />
| 16<br />
| 32<br />
| 256<br />
| Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz<br />
| '''Restricted access'''<br />
|-<br />
| dfg-xeon<br />
| 4<br />
| 16<br />
| 64<br />
| 64<br />
| Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz<br />
| '''Restricted access'''<br />
<br />
|}<br />
<br />
The access to the DFG-Nodes (dfg and dfg-big) is restricted to the members of the SFB/TR49. If you do not belong to that group but want to test and develop programs for the Infiniband Network, please talk to the administrator. The queue 'fplo' have the same restrictions like the dfg-queue and is intended for large memory and single threaded job from the program 'fplo'.<br />
The access to the queue 'quantum' is restricted to group Prof. Hofstetter.<br />
<br />
== Submitting Jobs ==<br />
<br />
In most case you want to submit a non interactive job to be executed in our cluster.<br />
<br />
This is very simple for serial (1 CPU) jobs:<br />
<br />
sbatch -p PARTITION jobscript.sh<br />
<br />
where jobscript.sh is a shell script with your job commands.<br />
<br />
Running '''openMPI''' jobs is not much more complictated:<br />
<br />
sbatch -p PARTITION -n X jobscript.sh<br />
<br />
where X is the number of desired MPI processes. Launch the job in the jobscript with:<br />
<br />
mpirun YOUREXECUTABLE<br />
<br />
You don't have to worry about the number of processes or specific nodes. Both slurm and openmpi know<br />
about each other.<br />
<br />
If you want '''infiniband''' for your MPI job (which is usually a good idea, if not running on the same node), you have to request the feature infiniband:<br />
<br />
sbatch -p dfg -C infiniband -n X jobscript.sh<br />
<br />
Note: Infiniband is only available for the partitions dfg and quantum.<br />
<br />
Running '''SMP jobs''' (multiple threads, not necessary mpi). Running MPI jobs an a single node, is recommended for the<br />
dfg-big nodes. This are big host, with up to 64 cpu's per node, but 'slow' gigabit network connection. Launch SMP jobs with<br />
<br />
sbatch -p PARTITION -N 1 -n X jobscript.sh<br />
<br />
=== Differences in network the network connection ===<br />
<br />
The new v3 dfg-xeon nodes are equipped with 10 GB network. This is faster (trough put) and has lower latency then gigabit ethernet, but is not is not as fast as the DDR infinband network. The 10 GB network is used for MPI and I/O. Infiniband is only use for MPI.<br />
<br />
== Defining Resource limits ==<br />
<br />
By default each job allocates 2 GB memory and a run time of 3 days. More resources can be requested by<br />
<br />
--mem-per-cpu=<MB><br />
<br />
where <MB> is the memory in megabytes. The virtual memory limit is 2.5 times of the requested real memory limit.<br />
<br />
The memory limit is not a hard limit. When exceeding the limit, your memory will be swapped out. Only when using more the 150% of the limit your job will be killed. So be conservative, to keep enough room for other jobs. Requested memory is blocked from the use by other jobs.<br />
<br />
-t or --time=<time><br />
<br />
where time can by "days-hours". See man page for more formats.<br />
<br />
<br />
== Memory Management ==<br />
<br />
In Slurm you specify only one parameter, which is the limit for your real memory usage and drives the decision where your job is started. The virtual memory of your job maybe 2.5 times of your requested memory. You can exceed you memory limit by 50%. But this will be swap space instead of real memory. This prevents crashing if you memory limit is a little to tight.<br />
<br />
== Inline Arguments ==<br />
<br />
sbatch arguments can be written in the jobfile:<br />
<br />
<pre><br />
#! /bin/bash<br />
#<br />
# Choosing a partition:<br />
#SBATCH -p housewives<br />
<br />
YOUR JOB COMMANDS....<br />
</pre><br />
<br />
= Links =<br />
<br />
* SLURM-Homepage [http://slurm.schedmd.com/slurm.html]</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=VPN_Access&diff=637VPN Access2015-12-09T14:37:16Z<p>Thomas: </p>
<hr />
<div>To get full access to our network from external locations we provide a VPN access based on openvpn. This is free software and part of every Linux distribution. The following guide has been tested with Ubuntu 12.04 to 15.10. It is available for Windows and MacOS too.<br />
<br />
=== Install OpenVPN === <br />
<br />
It is not part of the default installation, but can easily installed using apt. Enter the following commands:<br />
<br />
sudo apt-get install openvpn<br />
<br />
The requieres to enter your password to get super user previleges.<br />
<br />
=== Command line configuration ===<br />
<br />
This is fast and easy but requieres to enter commands. Create or download [http://th.physik.uni-frankfurt.de/~thw/vpn/all-via-itp.ovpn] the config file and store it anywhere you like:<br />
<br />
<pre><br />
client<br />
dev tap<br />
proto udp<br />
nobind<br />
remote vpn.th.physik.uni-frankfurt.de<br />
verify-x509-name vpn.th.physik.uni-frankfurt.de name<br />
remote-cert-tls server<br />
resolv-retry infinite<br />
auth-user-pass<br />
ca private-ca-itp.crt<br />
redirect-gateway def1 <br />
</pre><br />
<br />
Download our CA (Certificate of Authority) [http://th.physik.uni-frankfurt.de/~thw/vpn/private-ca-itp.crt] and store it in the same place. This file is needed for verifcation the authenticity of the server.<br />
<br />
This configuration routes all traffic trough ITP, this is usful if you want to download papers, which are restricted to the university network.<br />
The second examples only routes the traffic going directly to the ITP trough the VPN and leavs your default gateway untouched. The only differenc is the missing 'redirect-gateway' statment [http://th.physik.uni-frankfurt.de/~thw/vpn/itp.vpn].<br />
<br />
<pre><br />
<br />
client<br />
dev tap<br />
proto udp<br />
nobind<br />
remote vpn.th.physik.uni-frankfurt.de<br />
verify-x509-name vpn.th.physik.uni-frankfurt.de name<br />
remote-cert-tls server<br />
resolv-retry infinite<br />
auth-user-pass<br />
ca private-ca-itp.crt<br />
</pre><br />
<br />
=== Start the VPN connection ===<br />
<br />
Open a terminal and change to the path where the vpn config file is stored. Start the connection with<br />
<br />
sudo openvpn itp.ovpn<br />
<br />
where itp.ovpn is the name of the config file. openvpn need root access, therefor you must enter your local password for sudo. After this you have to enter your ITP credentials (Username and Password).<br />
<br />
If everything went fine the output will look like:<br />
<br />
<pre><br />
Fri Dec 7 15:03:00 2012 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).<br />
Fri Dec 7 15:03:00 2012 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables<br />
Fri Dec 7 15:03:00 2012 UDPv4 link local: [undef]<br />
Fri Dec 7 15:03:00 2012 UDPv4 link remote: [AF_INET]141.2.246.2:1194<br />
Fri Dec 7 15:03:00 2012 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this<br />
Fri Dec 7 15:03:00 2012 [FIAS-ITP_Generic_VPN_Service] Peer Connection Initiated with [AF_INET]141.2.246.2:1194<br />
Fri Dec 7 15:03:02 2012 TUN/TAP device tap0 opened<br />
Fri Dec 7 15:03:02 2012 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0<br />
Fri Dec 7 15:03:02 2012 /sbin/ifconfig tap0 10.63.131.1 netmask 255.255.0.0 mtu 1500 broadcast 10.63.255.255<br />
Fri Dec 7 15:03:02 2012 Initialization Sequence Completed<br />
</pre><br />
<br />
Termiate the session by pressing Ctrl-C in this terminal.<br />
<br />
=== Hacking around firewalls ===<br />
<br />
If you have problems with firewalls, we provide some oder ports und protocols to circumvent these firewalls<br />
<br />
{|border="1"<br />
|-<br />
!Proto<br />
!Port<br />
|-<br />
| tcp<br />
| 1194<br />
|-<br />
|tcp<br />
| 80<br />
|-<br />
|udp<br />
|53<br />
|}</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=VPN_with_Networkmanager&diff=636VPN with Networkmanager2015-12-01T16:15:05Z<p>Thomas: </p>
<hr />
<div>This article shows you how to log into our VPN network without using the terminal. This method is by far more convenient and you also may find this helpful, if you are not very familiar with command lines. <br />
We will use a VPN Plugin called network-manager.<br />
<br />
==Installation==<br />
<br />
Open up a terminal of your choice (Ctrl + T) and install OpenVPN Network Manager by tying the following line:<br />
<br />
sudo apt-get install network-manager-openvpn-gnome<br />
<br />
Please enter your password to confirm the installation.<br />
<br />
After the successful installation NetworkManager must be restartet:<br />
<br />
sudo service network-manager restart<br />
<br />
Again, confirm with your password if necessary. <br />
<br />
== Getting Started ==<br />
<br />
<br>[[File:step_01.png|thumb|x50|Ubuntu 14.04]]<br />
<br />
To get VPN access you must set up a new VPN connection first. Click on the two arrow symbol (or the WiFi symbol - depending on which connection you are currently using) in the top right corner. <br />
: Now choose <code>VPN Connections -> Configure VPN...</code>. <br><br />
A new window will open up. <br />
: Click on <code>Add</code> to add a new connection. <br><br />
You will be asked for the connection type. <br />
: Choose <code>OpenVPN</code> and click on <code>Create...</code>.<br />
Now you have to edit and configure your connection. Choose any connection name e.g. itp_openvpn. <br><br />
<br />
For the '''Gateway''' type:<br />
vpn.th.physik.uni-frankfurt.de<br />
Under '''Authentication''' select <code>Password</code> as authentication type. Enter your user name and password and choose the CA Certificate 'private-ca-itp.crt'. It can be downloaded [http://th.physik.uni-frankfurt.de/~thw/vpn/private-ca-itp.crt here].<br />
<br />
<br>[[File:step_04.png|thumb|left|x50|VPN Settings]]<br />
Save your changes.<br />
<br />
Your new VPN connection will be listet in '''Network Connections'''.<br />
<br />
==Using a VPN Connection==<br />
To access a VPN network just click on the arrow or WiFi symbol on the top right corner. Your configured connection should be found under '''VPN Connections'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=VPN_with_Networkmanager&diff=635VPN with Networkmanager2015-12-01T16:14:29Z<p>Thomas: </p>
<hr />
<div>This article shows you how to log into our VPN network without using the terminal. This method is by far more convenient and you also may find this helpful, if you are not very familiar with command lines. <br />
We will use a VPN Plugin called network-manager.<br />
<br />
==Installation==<br />
<br />
Open up a terminal of your choice (Ctrl + T) and install OpenVPN Network Manager by tying the following line:<br />
<br />
sudo apt-get install network-manager-openvpn-gnome<br />
<br />
Please enter your password to confirm the installation.<br />
<br />
After the successful installation NetworkManager must be restartet:<br />
<br />
sudo service network-manager restart<br />
<br />
Again, confirm with your password if necessary. <br />
<br />
== Getting Started ==<br />
<br />
<br>[[File:step_01.png|thumb|x50|Ubuntu 14.04]]<br />
<br />
To get VPN access you must set up a new VPN connection first. Click on the two arrow symbol (or the WiFi symbol - depending on which connection you are currently using) in the top right corner. <br />
: Now choose <code>VPN Connections -> Configure VPN...</code>. <br><br />
A new window will open up. <br />
: Click on <code>Add</code> to add a new connection. <br><br />
You will be asked for the connection type. <br />
: Choose <code>OpenVPN</code> and click on <code>Create...</code>.<br />
Now you have to edit and configure your connection. Choose any connection name e.g. itp_openvpn. <br><br />
<br />
For the '''Gateway''' type:<br />
vpn.th.physik.uni-frankfurt.de<br />
Under '''Authentication''' select <code>Password</code> as authentication type. Enter your user name and password and choose the CA Certificate 'localca.full.pem'. It can be downloaded [http://th.physik.uni-frankfurt.de/~thw/vpn/private-ca-itp.crt here].<br />
<br />
<br>[[File:step_04.png|thumb|left|x50|VPN Settings]]<br />
Save your changes.<br />
<br />
Your new VPN connection will be listet in '''Network Connections'''.<br />
<br />
==Using a VPN Connection==<br />
To access a VPN network just click on the arrow or WiFi symbol on the top right corner. Your configured connection should be found under '''VPN Connections'''.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=VPN_Access&diff=634VPN Access2015-12-01T16:13:15Z<p>Thomas: </p>
<hr />
<div>To get full access to our network from external locations we provide a VPN access based on openvpn. This is free software and part of every Linux distribution. The following guide has been tested with Ubuntu 12.04 to 15.10. It is available for Windows and MacOS too.<br />
<br />
=== Install OpenVPN === <br />
<br />
It is not part of the default installation, but can easily installed using apt. Enter the following commands:<br />
<br />
sudo apt-get install openvpn<br />
<br />
The requieres to enter your password to get super user previleges.<br />
<br />
=== Command line configuration ===<br />
<br />
This is fast and easy but requieres to enter commands. Create or download [http://th.physik.uni-frankfurt.de/~thw/vpn/itp.ovpn] the config file and store it anywhere you like:<br />
<br />
<pre><br />
client<br />
dev tap<br />
proto udp<br />
nobind<br />
remote vpn.th.physik.uni-frankfurt.de<br />
verify-x509-name vpn.th.physik.uni-frankfurt.de name<br />
remote-cert-tls server<br />
resolv-retry infinite<br />
auth-user-pass<br />
ca private-ca-itp.crt<br />
redirect-gateway def1 <br />
</pre><br />
<br />
Download our CA (Certificate of Authority) [http://th.physik.uni-frankfurt.de/~thw/vpn/private-ca-itp.crt] and store it in the same place. This file is needed for verifcation the authenticity of the server.<br />
<br />
This configuration routes all traffic trough ITP, this is usful if you want to download papers, which are restricted to the university network.<br />
The second examples only routes the traffic going directly to the ITP trough the VPN and leavs your default gateway untouched. The only differenc is the missing 'redirect-gateway' statment.<br />
<br />
<pre><br />
<br />
client<br />
dev tap<br />
proto udp<br />
nobind<br />
remote vpn.th.physik.uni-frankfurt.de<br />
verify-x509-name vpn.th.physik.uni-frankfurt.de name<br />
remote-cert-tls server<br />
resolv-retry infinite<br />
auth-user-pass<br />
ca private-ca-itp.crt<br />
</pre><br />
<br />
=== Start the VPN connection ===<br />
<br />
Open a terminal and change to the path where the vpn config file is stored. Start the connection with<br />
<br />
sudo openvpn itp.ovpn<br />
<br />
where itp.ovpn is the name of the config file. openvpn need root access, therefor you must enter your local password for sudo. After this you have to enter your ITP credentials (Username and Password).<br />
<br />
If everything went fine the output will look like:<br />
<br />
<pre><br />
Fri Dec 7 15:03:00 2012 WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).<br />
Fri Dec 7 15:03:00 2012 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables<br />
Fri Dec 7 15:03:00 2012 UDPv4 link local: [undef]<br />
Fri Dec 7 15:03:00 2012 UDPv4 link remote: [AF_INET]141.2.246.2:1194<br />
Fri Dec 7 15:03:00 2012 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this<br />
Fri Dec 7 15:03:00 2012 [FIAS-ITP_Generic_VPN_Service] Peer Connection Initiated with [AF_INET]141.2.246.2:1194<br />
Fri Dec 7 15:03:02 2012 TUN/TAP device tap0 opened<br />
Fri Dec 7 15:03:02 2012 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0<br />
Fri Dec 7 15:03:02 2012 /sbin/ifconfig tap0 10.63.131.1 netmask 255.255.0.0 mtu 1500 broadcast 10.63.255.255<br />
Fri Dec 7 15:03:02 2012 Initialization Sequence Completed<br />
</pre><br />
<br />
Termiate the session by pressing Ctrl-C in this terminal.<br />
<br />
=== Hacking around firewalls ===<br />
<br />
If you have problems with firewalls, we provide some oder ports und protocols to circumvent these firewalls<br />
<br />
{|border="1"<br />
|-<br />
!Proto<br />
!Port<br />
|-<br />
| tcp<br />
| 1194<br />
|-<br />
|tcp<br />
| 80<br />
|-<br />
|udp<br />
|53<br />
|}</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Storage_and_Backup&diff=234Storage and Backup2009-03-04T17:01:59Z<p>Thomas: </p>
<hr />
<div>== Storage ==<br />
<br />
There are different file systems with different lifetime and redundancy which you can use to store your data. <br />
<br />
;your home directory<br />
:This is your primary directory where all settings, your Mail and other important data is saved. It is mounted on every host to /home/YOUR_LOGIN. A backup is done nightly. This file system has an individual limit which you can check with the command 'df'. In change to earlier setups it has no soft limit which you can exceed for a few days.<br />
<br />
;/tmp&nbsp;<br />
:This is the counterpart to your home. It is located on the local disk and should be used for temporary data. Unused files are delete after 14 days.<br />
<br />
;/home/work-itp<br>/home/work-itp2<br />
:This directories are globally accessible and can be used by everyone for minor important data which are not worth to be backed up or simply to large for home. This files are not deleted, but if the disk is full we tell you to delete some files. It runs on an raid5 system, that means a disk failure will not result in data loss. It is also served by a dedicated machine (the old tantalos) and heavy load does not affect the home directories. If you want to use this space please create a sub directory with you login name.<br />
<br />
:The new work-itp2 is powered by two Raid-Boxes, kindly provided the HRZ. They internally form a raid5 and are merged under the host to a raid0 (striping), which can be called a raid 50 and results in a disk throughput of near 2Gb/s. To give this performance to the network the host is connected with two Gigabit uplinks using channel bonding. Benchmarks with NFS has shown that we do not relay get much more performance than a 1Gb link. The reason is the the cpu's in the host are two weak. If we can get a stronger machine, this will be upgraded in the future.<br />
<br />
== Backup ==<br />
<br />
Backups of the home directory and several other important system directories is done nightly.<br />
<br />
*There are held '''3''' generations of a file.<br />
*Overwritten files are stored for '''90''' days<br />
*A deleted file is stored for '''90''' days<br />
<br />
If you have delete some files and want them restored, please contact the system administrator.</div>Thomashttps://itp.uni-frankfurt.de/wiki-it/index.php?title=Storage_and_Backup&diff=233Storage and Backup2009-03-04T17:01:41Z<p>Thomas: </p>
<hr />
<div>== Storage ==<br />
<br />
There are different file systems with different lifetime and redundancy which you can use to store your data. <br />
<br />
;your home directory<br />
:This is your primary directory where all settings, your Mail and other important data is saved. It is mounted on every host to /home/YOUR_LOGIN. A backup is done nightly. This file system has an individual limit which you can check with the command 'df'. In change to earlier setups it has no soft limit which you can exceed for a few days.<br />
<br />
;/tmp&nbsp;<br />
:This is the counterpart to your home. It is located on the local disk and should be used for temporary data. Unused files are delete after 14 days.<br />
<br />
;/home/work-itp<br>/home/work-itp2<br />
:This directories is globally accessible and can be used by everyone for minor important data which are not worth to be backed up or simply to large for home. This files are not deleted, but if the disk is full we tell you to delete some files. It runs on an raid5 system, that means a disk failure will not result in data loss. It is also served by a dedicated machine (the old tantalos) and heavy load does not affect the home directories. If you want to use this space please create a sub directory with you login name.<br />
<br />
:The new work-itp2 is powered by two Raid-Boxes, kindly provided the HRZ. They internally form a raid5 and are merged under the host to a raid0 (striping), which can be called a raid 50 and results in a disk throughput of near 2Gb/s. To give this performance to the network the host is connected with two Gigabit uplinks using channel bonding. Benchmarks with NFS has shown that we do not relay get much more performance than a 1Gb link. The reason is the the cpu's in the host are two weak. If we can get a stronger machine, this will be upgraded in the future.<br />
<br />
== Backup ==<br />
<br />
Backups of the home directory and several other important system directories is done nightly.<br />
<br />
*There are held '''3''' generations of a file.<br />
*Overwritten files are stored for '''90''' days<br />
*A deleted file is stored for '''90''' days<br />
<br />
If you have delete some files and want them restored, please contact the system administrator.</div>Thomas