WARNING: exceeding the disk quota in your home ($HOME) may induce damage to configuration files
When rewriting a configuration file, a lot of utilities will remove the old file and create a new one.
The removal will get done without problem, but the writing of the new file may fail due to an exceeded quota.
a) Check your home quota with the command: |
b) Find your large files and directories du -hsc ~/.[a-z]* ~/* |
c) (Re)move files and directories 1. Remove whatever you do not need anymore. (this is a form of infinite compression) 2. Put whatever does not need to be in your home under your data space. (e.g. /snow /zwack ....) 3. Use /extras/$USER Move large software directories like .local, .cache, .python, etc. to /extras/$USER/ to move directory abc : cd $HOME mv abc /extras/$USER/. # move the directory ln -s /extras/$USER/abc abc # create a "soft link" in $HOME cd $HOME/abc will still bring you to that directory but will not affect your HOME quota |
A simple way to check if your display forwarding is okay is to execute the command:
xclock
If this opens a little window with a clock your setup is good.
If you do not get the little clock window check the following:
a) When using ssh make sure you used it either with the ' -Y ' key (plus -C for better compression)!
ssh -YC ...
b) Check your home quota with (see "Disk quota exceeded in your home" above for more info):
quota
If you are over quota in your home you cannot open any windows. To reduce the data in your home check point "Disk quota exceeded in your home" above.
Error message:
"stack overflow: thread 0, max 10228KB, used 1147KB, request 37324944B"
=> unlimit your stack by setting:
ulimit -s unlimited
Error message:
"X11 connection rejected because of wrong authentication."
You might be over your quota in your HOME.
Check with: quota -v
Error message:
"Error: Can't open display: localhost:..."
Connect with "ssh -Y ..." instead of "ssh -X ...".