W nodes (2011)
Desktops
Department’s LAN
Other
System
Posted in Misc
If this is the first time you read this guide, you will need to install the program pyenv. This is done by typing the following commands:
1. Download pyenv
$ git clone git://github.com/yyuu/pyenv.git ~/.pyenv
2. Make pyenv configuration file (to source when you need to use it)
$ mkdir ~/env $ echo 'export PYENV_ROOT="$HOME/.pyenv"' > ~/env/pyenv $ echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/env/pyenv $ echo 'eval "$(pyenv init -)"' >> ~/env/pyenv
This section will show you how to install your own version of python. First you will have to decide which version of python you want to install. The de facto standard version of python today is 2.7.6 so this guide will show you how to install that version.
1. Get pyenv to install the python version of your liking.
$ pyenv install 3.4.0
2. Make the version you just installed to the standard version for every time you run python.
$ pyenv global 3.4.0
Now you should be all set. If you change your mind about which version of Python to use, just redo this section and choose a different version. You can also have multiple versions installed at the same time and just switch between them usuing ‘pyenv global’ as shown above, if you have a script that requires Python 3.x or any other version.
First, open a new terminal and run “$source ~/env/pyenv”. To be able to install your own python modules, you will first have to follow the sections ‘First time only’ and ‘Installing your own Python version’ above.
To install modules in your python, use pip
$ pip install [module name]
Example:
$ pip install numpy
Unpack the package if necessary (example for nanocut)
$ tar -xvzf nanocut-12.12.tar.gz $ cd nanocut-12.12
Then follow the installation instructions (example for nanocut)
$ python setup.py install
Run this after installing executables
$ pyenv rehash
In a new terminal source the pyenv setup
$ source ~/env/pyenv
Enjoy your own python version installation!
Within the pyenv (i.e. after you have sourced the configuration)
# List the available python environments that could be installed
$ pyenv versions --list
# Change to another version that you have installed
$ pyenv global 2.6.7
# Uninstall previously installed version
$ pyenv uninstall 3.3.3
$ pip freeze
$ pip list --outdated
$ pip install --upgrade SomePackage
Links:
http://www.uppmax.uu.se/how-to-install-your-own-python-modules-or-specific-python-version
https://aradi.bitbucket.org/nanocut/installation.htmlhttps://pypi.python.org/pypi/pip
Posted in Instructions, Internal
To install the “Client” that will allow you to print to Korint, follow the instructions on this page: http://www.korint.uu.se/korintClients/ . Refer to Linux/Mac/Windows links on the top right of the page.
After installation make sure that CUPS is not sharing the printer (it will share it by default).
Follow the instructions for the Windows IPP. This will work easier and will cause less troubles. Make sure you follow the instructions carefully – there are some patches that needs to be applied before installation. Also, read if there are some specific instructions for Windows7 or Windows8 (these change constantly)
Read this page “Get started“
Posted in Instructions
(Conference) better pointer /the last we bought seems to confuse people/ KENSINGTON S600I WIRELESS PRESENTATION REMOTE: http://www.dustin.se/product/5010103995/kensington-s600i-wireless-presentation-remote/
Posted in Misc
These instructions don’t cover obvious choices or ones that are too difficult to explain in a text this short. Ask if you have questions, but please try as much as you can yourself!
rpm -Uvh /home/public/SL6X/yum-conf-sl6x-1-711.noarch.rpm
rpm is the redhat package manager and the -Uvh flags mean upgrade, verbose, hash). The rpm-file rpm changes the locations of repositiories to point to the local mirror on mackmyra. They also change so we get automatic updates between minor releases (6.1, 6.2 …)
yum install yum-conf-epel
/home_local/daniels 192.168.0.0/24(rw,sync)
Posted in Instructions
Regenerate ssh hostkeys (SL60):
ssh-keygen -b 1024 -f /etc/ssh/ssh_host_key -N ”
ssh-keygen -b 1024 -f /etc/ssh/ssh_host_rsa_key -N ”
ssh-keygen -t dsa -b 1024 -f /etc/ssh/ssh_host_dsa_key -N ”
Posted in Instructions
sendmail masquerading setup on SL44 and SL50 and SL51 and SL52 and SL6X:
This configuration allows you to send mail from the command line. It also makes sure that mail sent to root on the local machine ends up on your email account.
Remove the dnl (which means delete to newline, and works as comment marker in m4) on the line with the SMART_HOST and change it to look like this:
define(`SMART_HOST’,`smtp.uu.se’)
MASQUERADE_AS(`kemi.uu.se')dnl FEATURE(masquerade_envelope)dnl
FEATURE(genericstable, `hash -o /etc/mail/genericstable') GENERICS_DOMAIN_FILE(`/etc/mail/genericsdomain')
hostname -f >/etc/mail/genericsdomain
root daniels@mkem.uu.se
logwatch daniels@mkem.uu.se
yum install sendmail-cf
and finally type make again.
# Person who should get root’s mail
root: daniels@mkem.uu.se
If you have problems with this, you can also check the logfile /var/log/maillog
Posted in Instructions
Your problem could be tackled in different ways, depending on the version of CUPS you’re running.
More recent versions of CUPS come with a builtin functionality that could help here. It’s called “ErrorPolicy”. It’s default setting is selected in cupsd.conf, and determines how cupsd should handle print queues which do not behave as expected. You have 3 choices to tag to each queue individually:
ErrorPolicy abort-job
ErrorPolicy retry-job
ErrorPolicy retry-this-job
ErrorPolicy stop-printer
abort-job
— Abort this job and proceed with next job in same queue
retry-job
— Retry this job after waiting for N seconds (where N is determined by cupsd.conf’s “JobRetryInterval” directive).
retry-this-job
— Retry current job immediately and indefinitely.
stop-printer
— Stop current print queue and keep the job for future printing. This is still the default, unless you define otherwise as per above mentioned alternatives It also was default + only possible behaviour for all queues in previous versions of CUPS (the one you do want to get rid of as per your question).
Additionally, you can set individual ErrorPolicies to each separate print queue. This setting would be noted in the printers.conf file. (Set it from a commandline with lpadmin -p printername -o printer-error-policy=retry-this-job).
For older versions of CUPS I’d recommend to have a look at beh, the CUPS BackEnd Handler. beh is a wrapper which can be applied to any CUPS backend.
Assuming your print queue currently has defined a backend of socket://192.168.1.111:9100
, and it behaves in the way you don’t like (being disabled by cupsd from time to time due to network connection problems). With beh you’d re-define your backend like this:
beh:/0/20/120/socket://192.168.1.111:9100
This would retry a job 20 times in two minute intervals, and disable the queue only when still not succeeding. Or you could do this:
beh:/1/3/5/socket://192.168.1.111:9100
This retries the job 3 times with 5 second delays between the attempts. If the job still fails, it is discarded, but the queue is not disabled. You want to let cupsd try indefinitely to connect to the device? Good, try this:
beh:/1/0/30/socket://192.168.1.111:9100
Try infinitely until printer comes back. Intervals between connection attempts are 30 seconds. The job does not get lost when the printer is turned off. You can intentionally delay printing simply by switching off the printer. A good configuration for desktop printers and/or home users.
Overall, there is no need to mess around with bash scripts, cron jobs, lpadmin, cupsenable or sudo in order to re-activate CUPS queues going down erratically.
Posted in Support
Mount your new disk on your computer as /home_local or something very similar to that.
Copy data from the lagavulin fileserver either over NFS (without removing any files!):
rsync -av /home/USER/ /home_local/USER/
or over ssh directly from lagavulin:
rsync -av -e “ssh -c blowfish” lagavulin:/home1/USER/ /home_local/USER/
You can do the above when you contiune to work as usual. To do the final transfer you should also use the –delete option to rsync which remove the old files on the target if they don’t exist on the source anymore, i.e.
rsync -av –delete /home/USER/ /home_local/USER/
When doing this it is best to not be logged on and use a lot of programs. Perhaps simply logging in through a text console is the best.
Make sure that the source and target are in the correct order!
When this has been done contact someone to make sure the NFS export is working, the auto.home and auto.backup files are correct and to issue the correct commands to put the information in the NIS tables.
To do the final backup I have a script in my home directory which looks like this and is named backup.sh which I run periodically:
#!/bin/sh BHOST="auchentoshan" if [ "`hostname`" == "$BHOST" ]; then time rsync -e "ssh -c blowfish" -av --delete /home/daniels/ lagavulin:/home1/daniels/ else echo This is not host $BHOST fi
In this case you should also ensure that you get the correct order for source and target directories!
Posted in Support
Inter-division beach volley tournament - first place award