So we have contacted you, and we have agreed on what to move where. Here's what will happen now.

1. Once you've told us what to move and where to move it, our servers will start copying data over.

But even when that is done, you won't be moved unless you log off from all LWPs.

2. So at some point in time, you log off entirely, from all LWPs, when you leave from work in the evening.

3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for <code>/project</code> are no longer where they were. They are now in <code>/project/whatever_name_we_agreed_on</code>.

Please note that
ls /project
will not show anything. Only when you actually access a directory under <code>/project</code> will it be mounted and shown.

===Danger!===

Do not access <code>/project/whatever_name_we_agreed_on/moved-dirs</code> until <code>~/moved-dirs</code> have vanished from your home directory.
While <code>~/moved-dirs</code> still exist, the copy under <code>/project</code> is just that: a copy. It may lag behind, or be incomplete, or be currently written by our scripts, or all of these. By accessing it, you now have modifications in both copies. That constitutes a mess, and since we warned you, it is you who gets to sort it out.

Once <code>~/moved-dirs</code> have vanished, your account has been migrated, and the new path under /project is the only one. Only then is is fine to use it.

===Handy symlinks===

Once you have been migrated (and not sooner, see the danger above), you could create symlinks from the old location to the new one:
ln -sT /project/whatever_name_we_agreed_on/somedir ~/somedir
There are programs that will treat a symlink differently from an ordinary file or directory, but most will keep working as if nothing had happened.

Over 50GB

2018-06-19T12:11:19Z

Jurjen:

Over 50GB

2018-06-19T12:10:35Z

Jurjen:

Over 50GB

2018-06-19T12:03:54Z

Jurjen: Created page with "So we have contacted you, and you are reading this. Your account is so big, the data doesn't fit in your quota on the new server. How to proceed? 1. Decide what to move else..."

So we have contacted you, and you are reading this.

Your account is so big, the data doesn't fit in your quota on the new server. How to proceed?

1. Decide what to move elsewhere.
For your (and our) convenience, we have created the file $HOME/migration/du. It lists the sizes of your subdirectories.
We have also created $HOME/migration/proposed. It looks like this:

79828 /research
32987 /rawdata
------ cut here - dirs below add up to less than 49000MB -------
9159 /edu
7428 /MyBackups
4113 /.thunderbird
3228 /educonf18

That's just a suggestion. Please feel free to select different directories than we did. But do tell us what to move.

2. Decide where to move it. Please see [[Project_Directories]].

3. Once you've told us what to move and where to move it, our servers will start copying data over.
4. Once the data is copied, we mark your account for migration.
5. At a moment when you are logged off (from all LWPs, not just your own), your account will be migrated.

6. The next time you log in, your home directory will not contain the project directories any more. They will be under /project/whatever_name_we_agreed_on.

Please not that ls /project will not show anything. Only when you actually access a directory under /project will it be mounted and shown.

When you are migrated, not only will your home directory server be on another server, some data will now be under /project

2018-06-13T12:34:34Z

Jurjen:

In June 2018, we start to enforce quota on the home directory servers.

'''Q:''' How much quotum do I have?

'''A:''' Usually 50GB. But see the next question. If you had more space in use when we moved you, your quotum is usage + 10GB. But we'll reduce it in the future, as you move stuff to /projects.

'''Q:''' How much of that is free?

'''A:''' Ask a shell:
quota
It will tell you how much you have, and how much is in use.

'''Q:''' What if I exceed my quotum?

'''A:''' You won't be able to write any more. (But other users still will. That's the point.)

'''Q:''' I need more space. What do I do?

'''A:''' You contact lwp@rug.nl. We give you space under /project. To do it, we need thes questions answered:
* '''Name:''' What should we call that directory under /project?
* '''Size:''' How much space do you need? If we need to set up an entire new server for you, especially consider the next question.
* '''Pay''': Who is authorizing that use? (Cc: to supervisor, Demand Manager or whomever)
* '''Removal''': When can we discard that data? If never, consider the next question.
* '''Succession''': You are going to be the owner of that project directory. Three months after your account is revoked, we remove the data. If that should not happen, tell us whom to give it to.

'''Q:''' I exceeded my quota. All my programs started complaining, and I can't work any more. I can't even log in any more.

'''A:''' That's a pity. In the worst case, press <CTR><F2> to get to a text-mode prompt. Log in, and delete some stuff until there is free space. After you logged out, <CTRL><F7> to get back to a graphics mode screen, and perhaps reboot. You should be able to work again.

'''Q:''' Quota are a nuisance! Why do we have to have them!?!

'''A:''' If large file systems break, fixing them takes weeks. So we want small filesystems. But if one single user writes too much data, all your lwps stop working. And on a small filesystem, the risk is considerable.

'''Q:''' Why this artificial split between $HOME and /project?

'''A:''' All your programs (shells, editors, browsers, mail, Matlab, etc. etc.) write to $HOME by default. If $HOME is full, all of those break, and some corrupt their data - silently, if you have bad luck. We '''don't''' want this for any significant number of users.
If /project (or part of it) overflows, only the programs break that were specifically directed to it. That's still bad, but not at all as bad as all your programs failing.

Quota

2018-06-13T12:34:18Z

Jurjen:

2018-04-30T08:47:29Z

Jurjen:

Installing your LWP

2015-09-17T14:14:41Z

Jurjen: Clarify that sda2 *will* be taken by Linux

[[Category:install-faq]]
The LWP can be (re)installed by the user. For a dual-boot installation you will need at least 180GB of HDD space. The LWP will claim 80GB and the UWP 100GB. The procedure differs for LWP-only and dual-boot systems, but for both (and actually any and all) cases, it is recommended to make a backup of all your locally stored data. The following has to be done to reinstall your system. 
 
'''Make a backup of your data on the hard-disk, if any, and restart your PC!'''
:'''LWP only'''
:''If you are upgrading from LWP1 to LWP2, it is necessary to remove the previous partitions from your harddisk first! LWP2 claims more space on the harddrive, than LWP1 did, so it will not fit within the old partitions and give an error if you try to install it anyway. [[Parted Magic | Here]]'s an explanation on how do that.''
:# At startup, press '''F12''' to boot from the network.
:# From the menu, choose '''Install LWP2'''. ''(password = iamsure)''
:# The installation can take up to ~90 minutes depending on your machine.
:# Press '''Enter''' to finish and restart the computer.
:# When the LWP starts for the first time it will display a message on the login screen telling you what is still being configured. This should disappear after 5-10 minutes and should not appear on subsequent boots.
:'''Dual-boot'''
:''If only the LWP has to be reinstalled follow the procudure for '''LWP only'''.''
:# Ask the servicedesk to install the UWP2 on your machine.
:#:'''Note!''' When using the unattended install for the UWP2, '''first''' create a 100GB primary partition on the HDD before starting the unattended installation, else it will create a 100mb partition in front of the 100GB partition, and if that happens, the actual Windows partition will be in the second primary partition slot (sda2 in Linux parlance). That would be bad, because the LWP installer installs into sda no matter what. So, with 100GB in a partition in the first slot, when installing the UWP2, select that partition you created to install it in. Now Linux will install (as always) into the second slot, and both OSes will coexist.
:# Follow the procudure for '''LWP only'''.

Using newer gcc in /opt/netapps

2015-09-01T08:41:01Z

Jurjen:

[[Category:software-faq]]

Gcc-5.2 is in /opt/netapps/gnu/gcc/5.2. In order for you to use it, this may have to be appended to your .profile:

GCCSNIPPET=/opt/netapps/gnu/gcc/5.2/sourceme
[ -r ${GCCSNIPPET} ] && . ${GCCSNIPPET}

Please note: /opt is *NOT* in ld.so.conf, and should not be

The environment variables that are set in the sourceme snippet influence Make-like programs (GNU make, icmake). So projects using such utilities will automatically build your programs using the newer compiler.

If you want to build by calling the compiler directly, you cannot just call 'g++'. Instead, call the newer compiler as $CXX, like this:

${CXX} -o hello hello.cc

NB: if you are reading this page as a participant (or attendee) of the C++ course, please ask your questions on the mailing list first, not through the Service Desk.

== Later versions ==
You may find that still later versions are available. Check /opt/netapps/gnu/gcc, and alter the above script by adjusting the line

GCCBASE="/opt/netapps/gnu/gcc/5.2"

Using newer gcc in /opt/netapps

2015-09-01T08:39:55Z

Jurjen:

[[Category:software-faq]]

Gcc-5.2 is in /opt/netapps/gnu/gcc/5.2. In order for you to use it, this may have to be appended to your .profile:

GCCSNIPPET=/opt/netapps/gnu/gcc/5.2/sourceme
[ -r ${GCCSNIPPET} ] && . ${GCCSNIPPET}

Please note: /opt is *NOT* in ld.so.conf, and should not be

The environment variables that are set in the sourceme snippet influence Make-like programs (GNU make, icmake). So projects using such utilities will automatically build your programs using the newer compiler.

If you want to build by calling the compiler directly, you cannot just call 'g++'. Instean, call the newer compiler as $CXX, like this:

${CXX} -o hello hello.cc

NB: if you are reading this page as a participant (or attendee) of the C++ course, please ask your questions on the mailing list first, not through the Service Desk.

== Later versions ==
You may find that still later versions are available. Check /opt/netapps/gnu/gcc, and alter the above script by adjusting the line

GCCBASE="/opt/netapps/gnu/gcc/5.2"

Using newer gcc in /opt/netapps

2015-09-01T07:54:59Z

Jurjen:

2015-02-10T19:07:03Z

Jurjen:

[[Category:Main]]
= LWP Wiki =
Welcome to the LWP-Wiki! For general LWP information, [http://www.rug.nl/cit/doelgroepen/medewerkers/lwp/index the LWP main page] is the starting point. 
If you're having trouble on your LWP, our [[FAQ]] is a good place to take a look first. We might already have solved your problem once or twice before. 
We're also trying to keep a [http://lwp-wiki.hosting.rug.nl/planning LWP Projects] page up to date. If you have something that needs to be added or changed on the LWP, take a look [http://lwp-wiki.hosting.rug.nl/planning there] first, perhaps we're already working on it.

== Announcements ==
{{Announcement| [[User:Chris|Chris]] ([[User talk:Chris|talk]]) 15:51, 28 January 2015 (CET)| We've recreated the lwp-wiki, with up to date pages and info. You can now subscribe to the wiki and add the main page to your watchlist, then you will receive an email whenever we update the main page with a new announcement.}}
 

== Contact ==
If you're having trouble with your LWP and the solution isn't in our [[FAQ]], contact us by using the '''support''' program on the LWP's (if possible) by entering "support" on a LWP command line or selecting it from the menu. 
For more general questions you can contact us by sending a mail to [mailto:lwp@rug.nl lwp@rug.nl].