linux
Zitat des Tages
Have you ever noticed that the system administrator's job seems to have two states applied to it? That they're either ignored or hated.
Zitiert aus Linux Clustering: Building and Maintaining Linux Clusters
Links des Tages
C3 (Cluster Command and Control)
http://www.csm.ornl.gov/torc/C3/
Befehle verteilt auf mehreren Computern ausführen
OpenPBS (Portable Batch System)
http://www.mcs.anl.gov/research/projects/openpbs/
Torque
http://www.csm.ornl.gov/torc/
Condor
http://www.cs.wisc.edu/condor/
Maui
http://www.clusterresources.com/products/maui-cluster-scheduler.php
German
http://www.danga.com/gearman/
Low-latency remote function execution. Run code remotely, in parallel, load balanced, in other languages, etc.
Zombies
Woher kommen Zombie-Prozesse und wie wird man sie wieder los? Bereits vor einiger Zeit bin ich über eine sehr gute englische Beschreibung gestolpert:
A process fully terminates when two events have booth happened: (1) the process itself has exited (or has been killed by a signal), and (2) its parent has executed a wait system call to find out what happened. A process that has exited or has been killed, but whose parent has not (yet) done a wait for it, enters a kind of suspended animation, ometimes known as zombie state. It is prevented from beeing scheuled and has its alarm timer turned off (if it was on), but it is not removed from the process table. Its memory is freed. Zombie state is temporary and rarely lasts long. When the parent finally does the wait, the process table slot is freed, and the file system and kernel are informed. A problem arises if the parent of an exiting processs is itself already dead. If no special action were taken, the exiting process would remain a zombie forever. Instead, the tables are changed to make it a child of the init process. When the system comes up, init reads the /etc/ttytab file to get a list of all terminals, and then forks off a login process to handle each one. It then blocks, waiting for processes to terminate. In this way, orphan zombies are cleaned up quickly.
Als Quelle habe ich das folgende Buch in Erinnerung, allerdings in einer etwas älteren Auflage:
Andrew S. Tanenbaum, Albert S. Woodhull; Operating Systems – Design and Implementation
Zitat des Tages
Neulich im Zoo in der Arktisabteilung:
Guck mal Papi – da sind Linuxe
LPIC Zertifizierung
Durch Zufall bin ich über ein anscheinend recht gute Quelle (in Englisch) zu den LPIC Zertifizierungen gestoßen:
LPIC-1 http://www.ibm.com/developerworks/linux/library/l-lpic1-v3-map/
LPIC-3 http://www.ibm.com/developerworks/linux/tutorials/l-lpic3301/
Filedescriptoren in Shellscripten
Interessanter Hinweis für Filedescriptoren in Shellscripten:
Meist installiertes Betriebssystem
Linux wird nie das meistinstallierte Betriebssystem sein. Bedenken Sie nur,
wie oft man Windows neu installieren muss!
Neue ATI Treiber unter openSuSE 10.3 x86_64
Linux Proprietary Driver – Catalyst 8.11 Release: x86 and x86_64 variants, heute installiert, läuft problemlos. Mir kommt die Darstellung der Fenster, besonders bei Multimediainhalten (beim Ziehen von Fenstern) etwas flüssiger vor.
Ich frage mich allerdings ob sich hier tatsächlich etwas geändert hat….
fglrxinfo
Vorher:
display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: Series OpenGL version string: 2.1.8201 Release
Nachher:
display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: Radeon X1650 Series OpenGL version string: 2.1.8201 Release
Kernel Kompilieren unter SuSE Linux mit Hindernissen
# make oldconfig HOSTCC scripts/basic/fixdep In file included from /usr/include/sys/socket.h:35, from /usr/include/netinet/in.h:24, from /usr/include/arpa/inet.h:23, from scripts/basic/fixdep.c:117: /usr/include/bits/socket.h:311:24: error: asm/socket.h: No such file or directory make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2
Die Lösung dafür hat eine neu Installation des Paketes linux-kernel-headers-2.6.22-19 gebracht!