Und siehe da, bei jeder Email meldete spamd:

Jul 28 12:40:59 hera spamd[10391]: pyzor: check failed: internal error


Pyzor (ein nützliches Spamassasinplugin) schien jedoch ansich zu gehen:


root@hera:~/pyzor-0.5.0# pyzor discover
downloading servers from http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
root@hera:~/pyzor-0.5.0# pyzor ping
public.pyzor.org:24441 (200, 'OK')


Des Rätsels Lösung ist, das spamd und damit pyzor nicht als root laufen:


ps -aux
vmail 10390 1.0 3.1 136424 65192 ? SN 12:34 0:07 spamd child


Das bedeutet natürlich, das man es unter dem Benutzer vmail testen muss:


root@hera:/etc/mail/spamassassin# su vmail
sh-3.2$ pyzor dicover
Traceback (most recent call last):
File "/usr/bin/pyzor", line 8, in
pyzor.client.run()
File “/usr/lib/python2.5/site-packages/pyzor/client.py”, line 1022, in run
ExecCall().run()
File “/usr/lib/python2.5/site-packages/pyzor/client.py”, line 180, in run
os.mkdir(homedir)
OSError: [Errno 2] No such file or directory: ‘/home/vmail/.pyzor’
sh-3.2$ pyzor discover
Traceback (most recent call last):
File “/usr/bin/pyzor”, line 8, in
pyzor.client.run()
File “/usr/lib/python2.5/site-packages/pyzor/client.py”, line 1022, in run
ExecCall().run()
File “/usr/lib/python2.5/site-packages/pyzor/client.py”, line 180, in run
os.mkdir(homedir)
OSError: [Errno 2] No such file or directory: ‘/home/vmail/.pyzor’
sh-3.2$ exit
exit


Pyzor kann nicht nach /home/vmail schreiben, da es dieses Verzeichnis einfach nicht gibt:

Nach:


root@hera:/etc/mail/spamassassin# mkdir /home/vmail
root@hera:/etc/mail/spamassassin# chown vmail:vmail /home/vmail


rennt nun alles wieder:


root@hera:/etc/mail/spamassassin# su vmail
sh-3.2$ pyzor discover
downloading servers from http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x
sh-3.2$ pyzor ping
public.pyzor.org:24441 (200, 'OK')
sh-3.2$ exit


Auch im Log ist wieder ein PYZOR_CHECK zu finden:


Jul 28 12:49:54 hera spamd[11117]: spamd: result: Y 21 - DIGEST_MULTIPLE,FH_HELO_EQ_D_D_D_D, HELO_DYNAMIC_DHCP, HELO_DYNAMIC_IPADDR, HTML_MESSAGE, MIME_HTML_ONLY, PYZOR_CHECK, RAZOR2_CF_RANGE_51_100, RAZOR2_CF_RANGE_E8_51_100, RAZOR2_CHECK, RCVD_IN_PBL,RDNS_NONE, SARE_UNI, SPF_FAIL, TW_LX,TW_QO, URIBL_BLACK,URI_HEX scantime=4.5, size=4597, user=xxx, uid=2000, required_score=5.0, rhost=localhost.localdomain, raddr=127.0.0.1, rport=33550,mid=, autolearn=spam


Get:1 http://ftp2.de.debian.org lenny Release.gpg [1032B]
Get:2 http://ftp2.de.debian.org lenny/updates Release.gpg [1032B]
Get:3 http://ftp2.de.debian.org lenny Release [73.6kB]
Get:4 http://ftp2.de.debian.org lenny/updates Release [40.8kB]
Ign http://ftp2.de.debian.org lenny Release
Get:5 http://ftp2.de.debian.org lenny/main Packages [6853kB]
Get:6 http://ftp2.de.debian.org lenny/contrib Packages [87.2kB]
Get:7 http://ftp2.de.debian.org lenny/non-free Packages [108kB]
Get:8 http://ftp2.de.debian.org lenny/updates/main Packages [154kB]
Get:9 http://ftp2.de.debian.org lenny/updates/contrib Packages [20B]
Get:10 http://ftp2.de.debian.org lenny/updates/non-free Packages [20B]
Fetched 7318kB in 4s (1521kB/s)
Reading package lists… Done
W: GPG error: http://ftp2.de.debian.org lenny Release: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9AA38DCD55BE302B
W: There is no public key available for the following key IDs:
9AA38DCD55BE302B
W: You may want to run apt-get update to correct these problems

gibt es eine sehr einfache Lösung:

apt-get install debian-archive-keyring

Und damit beschwert sich apt-get nicht mehr über die Keys, da alle fehlenden Keys nun importiert wurden.

Um generell unter Ubuntu kompilieren zu können, sollte das Paket build-essential installiert sein. Nach der Installation der Ubuntu-Nvidia-Grafiktreiber (sind bereits aktuell) und des CUDA-Toolkits und SDK’s von der CUDA-Seite, gab es bei mir ein paar Probleme beim kompilieren der SDK-Beispiele:

1.

In file included from ./../common/inc/paramgl.h:13,
from src/paramgl.cpp:8:
./../common/inc/GL/glut.h:59:19: error: GL/gl.h: No such file or directory
./../common/inc/GL/glut.h:60:20: error: GL/glu.h: No such file or directory
In file included from ./../common/inc/paramgl.h:13,
from src/paramgl.cpp:8:
./../common/inc/GL/glut.h:433: warning: ‘glutUseLayer’ initialized and declared ‘extern’
./../common/inc/GL/glut.h:433: error: variable or field ‘glutUseLayer’ declared void
./../common/inc/GL/glut.h:433: error: ‘GLenum’ was not declared in this scope
./../common/inc/GL/glut.h:491: error: ‘GLfloat’ has not been declared
./../common/inc/GL/glut.h:491: error: ‘GLfloat’ has not been declared
./../common/inc/GL/glut.h:491: error: ‘GLfloat’ has not been declared
./../common/inc/GL/glut.h:492: error: ‘GLfloat’ does not name a type
./../common/inc/GL/glut.h:496: warning: ‘glutGet’ initialized and declared ‘extern’

Das Problem wird gelöst, in dem die Opengl-devel Pakete installiert werden: apt-get install libglut3-dev

2.

make[1]: Entering directory `/home/ich/NVIDIA_CUDA_SDK/projects/dxtc’
/usr/include/bits/stdio2.h(35): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(66): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(99): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(105): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(159): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(167): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(174): error: identifier “__builtin_va_arg_pack” is undefined
/usr/include/bits/stdio2.h(182): error: identifier “__builtin_va_arg_pack” is undefined


Diese Fehler hängen damit zusammen das Ubuntu 8.10 nicht offiziel unterstützt wird, bzw. genauer gesagt die gcc-version Probleme bereitet.

Ein Workaround der bei mir funktionierte:


sudo apt-get install gcc-4.2 g++-4.2
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.2 60 --slave /usr/bin/g++ g++ /usr/bin/g++-4.2


3. /usr/bin/ld: cannot find -lXmu

Lösung: xmu muss installiert werden


sudo apt-get install libxmu-dev libxmu6


4.

make[1]: Entering directory `/home/ich/NVIDIA_CUDA_SDK/projects/simpleTextureDrv’
In file included from /usr/include/features.h:354,
from /usr/cuda/bin/../include/host_config.h:53,
from /usr/cuda/bin/../include/cuda_runtime.h:45,
from :0:
/usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory
make[1]: *** [data/simpleTexture_kernel.cubin] Error 255
make[1]: Leaving directory `/home/ich/NVIDIA_CUDA_SDK/projects/simpleTextureDrv’
make: *** [projects/simpleTextureDrv/Makefile.ph_build] Error 2

Die Glibc-Pakete für 32-bit Anwendungen unter 64-bit fehlen (Der Fehler betrifft nur 64bit-Installationen)

sudo apt-get install libc6-dev-i386 libc6-i386


Nach diesen Korrekturen kompilierten alle Beispiele durch und die die ich bisher probierte starteten auch ohne Probleme auf meiner Geforce 260. Das Mandelbrot-Beispiel ließ meinen ganzen PC abstürzen und die Grafikkarte nur noch Fiebgeräusche von sich geben (!), hier vermute ich Compiz als übeltäter, den man wohl besser bei Cuda-Experimenten abschaltet.

rausfinden welche Platte betroffen ist:

mdadm -D /dev/mdX


Zu den betroffenen Partitionen wieder die zweite Platte einhängen:


mdadm /dev/md1 -a /dev/sdx1
mdadm /dev/md2 -a /dev/sdx2
...


Dann mit

cat /proc/mdstat


den Fortschritt überprüfen:


Personalities : [raid1]
md1 : active raid1 sdb1[1] sda1[0]
1959808 blocks [2/2] [UU]

md2 : active raid1 sdb2[2] sda2[0]
14659200 blocks [2/1] [U_]
resync=DELAYED

md3 : active raid1 sdb3[2] sda3[0]
471764672 blocks [2/1] [U_]
[>....................] recovery = 0.4% (2007104/471764672) finish=97.5min speed=80284K/sec

unused devices:


But now to the installation: I show it with the 64bit version of Debian Lenny.

After the installation of Lenny, install the custom Xen kernel and Xen-Tools:

apt-get install xen-linux-system-2.6.26-1-xen-amd64 xen-utils-3.2-1 lvm2 python-xml xen-tools

In order to bridge the virtual network devices of your guests to the host system, you need to edit the configuration file /etc/xen/xend-config.sxp

This part is relevant:


##
# To bridge network traffic, like this:
#
# dom0: ----------------- bridge -> real eth0 -> the network
# |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
(network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by default.
# To use a different one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
#
# The bridge is named xenbr0, by default. To rename the bridge, use
#
# (network-script 'network-bridge bridge=‘)
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain. To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
#(network-script network-dummy)


You must comment “(network-script network-dummy)” out as seen in the listing and remove the comment before “(network-script network-bridge)”

Now you can boot into your freshly installed Xen-Linux:
shutdown -r now

To check that everything works as expected run:

xm list Xm stands for Xen-management, a tool to manage your guest machines.

Is should say something like this:


olymp:~# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 3242 4 r----- 266.8


Domain-0 is your host system and you haven’t created any guests yet.

You can do that very easily with the xen-tools, that you’ve already installed. You can set your default preferences for it very easily in the file /etc/xen-tools/xen-tools.conf. To use Debian Lenny 64bit as default guest, use the following configuration:

1. ##
2. #  /etc/xen-tools/xen-tools.conf
3. ##
4. #
5. #  This is the global configuration file for the scripts included
6. # within the xen-tools package.
7. #
8. #  For more details please see:
9. #
10. #        http://xen-tools.org/
11. #
12. ##
13.  
14.  
15. ##
16. #
17. # File Format
18. # ———–
19. #
20. #  Anything following a ‘#’ character is ignored as a comment.
21. #
22. #  Otherwise the format of this file "key = value".  The value of
23. # any keys in this file may be constructed via the output of a command.
24. #
25. #  For example:
26. #
27. #         kernel = /boot/vmlinuz-`uname -r`
28. #
29. ##
30.  
31.  
32.  
33. #
34. ##
35. #  Output directory for storing loopback images.
36. #
37. #  If you choose to use loopback images, which are simple to manage but
38. # slower than LVM partitions, then specify a directory here and uncomment
39. # the line.
40. #
41. #  New instances will be stored in subdirectories named after their
42. # hostnames.
43. #
44. ##
45. dir = /home/xen
46. #
47.  
48. #
49. ##
50. #
51. # If you don’t wish to use loopback images then you may specify an
52. # LVM volume group here instead
53. #
54. ##
55. # lvm = skx-vg
56.  
57.  
58. #
59. ##
60. #
61. #  Installation method.
62. #
63. #  There are four distinct methods which you may to install a new copy
64. # of Linux to use in your Xen guest domain:
65. #
66. #   - Installation via the debootstrap command.
67. #   - Installation via the rpmstrap command.
68. #   - Installation via the rinse command.
69. #   - Installation by copying a directory containing a previous installation.
70. #   - Installation by untarring a previously archived image.
71. #
72. #  NOTE That if you use the "untar", or "copy" options you should ensure
73. # that the image you’re left with matches the ‘dist’ setting later in
74. # this file.
75. #
76. #
77. ##
78. #
79. #
80. # install-method = [ debootstrap | rinse | rpmstrap | copy | tar ]
81. #
82. #
83. install-method = debootstrap
84.  
85. #
86. # If you’re using the "copy", or "tar" installation methods you must
87. # need to specify the source location to copy from, or the source
88. # .tar file to unpack.
89. #
90. # You may specify that with a line such as:
91. #
92. # install-source = /path/to/copy
93. # install-source = /some/path/img.tar
94. #
95. #
96.  
97. #
98. ##
99. #  Command definitions.
100. ##
101. #
102. # The "rinse", and "rpmstrap" commands are hardwired into
103. # the script, but if you wish to modify the commands which are executed
104. # when installing new systems by a "copy", "debootstrap", or "tar" method
105. # you can do so here:
106. #
107. # (This allows you to install from a .tar.bz file, rather than a plain
108. # tar file, use cdebootstrap, etc.)
109. #
110. # install-method=copy:
111. # copy-cmd = /bin/cp -a $src/* $dest
112. ##
113. #install-method=debootstrap:
114. debootstrap-cmd=/usr/sbin/debootstrap
115. #
116. # install-method=tar:
117. # tar-cmd  = /bin/tar –numeric-owner -xvf $src
118. #
119. #
120.  
121.  
122.  
123. #
124. ##
125. #  Disk and Sizing options.
126. ##
127. #
128. size   = 4Gb      # Disk image size.
129. memory = 256Mb    # Memory size
130. swap   = 256Mb    # Swap size
131. # noswap = 1      # Don’t use swap at all for the new system.
132. fs     = ext3     # use the EXT3 filesystem for the disk image.
133. dist   = lenny     # Default distribution to install.
134. image  = sparse   # Specify sparse vs. full disk images.
135.  
136. #
137. #  Currently supported and tested distributions include:
138. #
139. # via Debootstrap:
140. #
141. #  Debian:
142. #   sid, sarge, etch, lenny.
143. #
144. #  Ubuntu:
145. #   edgy, feisty, dapper.
146. #
147. # via Rinse:
148. #   centos-4, centos-5.
149. #   fedora-core-4, fedora-core-5, fedora-core-6, fedora-core-7
150. #
151. #
152.  
153.  
154.  
155. ##
156. # Networking setup values.
157. ##
158.  
159. #
160. # Uncomment and adjust these network settings if you wish to give your
161. # new instances static IP addresses.
162. #
163. # gateway   = 192.168.1.1
164. # netmask   = 255.255.255.0
165. # broadcast = 192.168.1.255
166. #
167. # Uncomment this if you wish the images to use DHCP
168. #
169. dhcp = 1
170.  
171.  
172. ##
173. # Misc options
174. ##
175.  
176. #
177. # Uncomment the following line if you wish to disable the caching
178. # of downloaded .deb files when using debootstrap to install images.
179. #
180. # cache = no
181. #
182.  
183. #
184. # Uncomment the following line if you wish to interactively setup
185. # a new root password for images.
186. #
187. passwd = 1
188.  
189. #
190. # If you’d like all accounts on your host system which are not present
191. # on the guest system to be copied over then uncomment the following line.
192. #
193. # accounts = 1
194. #
195.  
196. #
197. # Default kernel and ramdisk to use for the virtual servers
198. #
199. kernel      = /boot/vmlinuz-`uname -r`
200. initrd      = /boot/initrd.img-`uname -r`
201.  
202. #
203. #  The architecture to use when using debootstrap, rinse, or rpmstrap.
204. #
205. #  This is most useful on 64 bit host machines, for other systems it
206. # doesn’t need to be used.
207. #
208. arch=amd64
209. #
210.  
211. #
212. # The default mirror for debootstrap to install Debian-derived distributions
213. #
214. mirror = http://ftp.de.debian.org/debian/
215.  
216. #
217. # A mirror suitable for use when installing the Dapper release of Ubuntu.
218. #
219. # mirror = http://gb.archive.ubuntu.com/ubuntu/
220.  
221. #
222. #  If you like you could use per-distribution mirrors, which will
223. # be more useful if you’re working in an environment where you want
224. # to regularly use multiple distributions:
225. #
226. # mirror_sid=http://ftp.us.debian.org/debian
227. # mirror_sarge=http://ftp.us.debian.org/debian
228. # mirror_etch=http://ftp.us.debian.org/debian
229. # mirror_dapper=http://archive.ubuntu.com/ubuntu
230. # mirror_edgy=http://archive.ubuntu.com/ubuntu
231. # mirror_feisty=http://archive.ubuntu.com/ubuntu
232. # mirror_gutsy=http://archive.ubuntu.com/ubuntu
233.  
234.  
235. #
236. #  Filesystem options for the different filesystems we support.
237. #
238. ext3_options   = noatime,nodiratime,errors=remount-ro
239. ext2_options   = noatime,nodiratime,errors=remount-ro
240. xfs_options    = defaults
241. reiser_options = defaults
242.  
243. #
244. #  Uncomment if you wish newly created images to boot once they’ve been
245. # created.
246. #
247. boot = 1
248.  
249.  
250. #
251. #  If you’re using the lenny or later version of the Xen guest kernel you will
252. # need to make sure that you use ‘hvc0′ for the guest serial device,
253. # and ‘xvdX’ instead of ’sdX’ for serial devices.
254. #
255. #  You may specify the things to use here:
256. #
257. serial_device = hvc0 #default
258. # serial_device = tty1
259. #
260. disk_device = xvda #default
261. # disk_device = sda
262. #
263.  
264.  
265. #
266. #  Here we specify the output directory which the Xen configuration
267. # files will be written to, and the suffix to give them.
268. #
269. #  Historically xen-tools have created configuration files in /etc/xen,
270. # and given each file the name $hostname.cfg.  If you want to change
271. # that behaviour you may do so here.
272. #
273. #
274. # output    = /etc/xen
275. # extension = .cfg
276. #
277. Download this code: xen-tools.conf

Now you can use:

xen-create-image --hostname test1 --role=udev

to install a new Debian Lenny as guest system. If everything went as it should, you should see your new client after that in “xm list”. Otherwise it doesn’t show up and you can try to manuelly create it with “xm create ” to see the error.

By the way “–role=udev” is needed, to install the package udev automatically in the guest. Without it, you can’t use ssh with your new guest and get the following error if you try to log in:


PTY allocation request failed on channel 0
stdin: is not a tty


If you use images for your guest (like shown here) you get very fast to the standard loopback limit of Debian Lenny. With that limit you can’t create more than 3 or 4 guests. It’s recommended to edit the file /etc/modprobe.d/local-loop (or create it) to adjust that limit:


options loop max_loop=64


Some more basics besides “xm list”: You can use “xm top” to monitor the activity of your guests (like top for processes). You can start, reboot and shutdown a guest with “xm start “, “xm reboot ” and “xm shutdown “.
You can enter a guest system directly with “xm console “. To exit the guest and go back to Dom0 use ctrl+]

For more commands you should read “xm help”

Das Problem ist folgendes (Text aus diesem bugtraq post):

If a Flash 9 SWF loads two SWF files with different SWF version
numbers from two distinct HTTP requests to the exact same URL
(including query string arguments), then Adobe's Flash Player plug-in
will try to dereference a null pointer


Die Lücke betrifft auch Version 10 (also die neuste) und man kann es hier selber testen:

http://flashcrash.dempsky.org/

Bei mir crashte Safari auch nach paar Sekunden unter Mac Os X, wenn es auch bei euch geht, postet euere System/Browser Kombination in den Kommentaren.

Hier ein kleines Howto um OpenVZ unter Debian Lenny einzurichten:

1. Installation:

apt-get install iproute libatm1 linux-image-2.6.26-1-openvz-amd64 linux-image-openvz-amd64 rsync vzctl vzquota


2. Anpassen der Datei /etc/sysctl.conf, dieser Abschnitt muss angefügt werden:

# On Hardware Node we generally need
# packet forwarding enabled and proxy arp disabled
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.ip_forward=1
# Enables source route verification
net.ipv4.conf.all.rp_filter = 1
# Enables the magic-sysrq key
kernel.sysrq = 1
# TCP Explict Congestion Notification
#net.ipv4.tcp_ecn = 0
# we do not want all our interfaces to send redirects
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.eth0.proxy_arp = 1


3. Diese neuen Regeln laden
sysctl -p

4. Nun kann man OpenVZ symbolisches nach /vz linken (Optional, aber hilfreich)
ln -s /var/lib/vz /vz

Am schnellsten hat man seine virtuelle Maschiene eingerichtet, wenn man sich ein Template aus diesem OpenVZ Template Repository aussucht. Diese Templates sind vorgefertigte Images der beliebtesten Distributionen, die ein sekundenschnelles Einrichten ermöglichen.

5. Nun ist es an der Zeit in das frische OpenVZ-System zu booten. Falls lilo verwendet wird, muss der Befehl lilo noch ausgeführt werden (Bei grub muss nichts gemacht werden)

shutdown -r now

6. z.b. das Debian Lenny Template:

cd /vz/template/cache und wget http://download.openvz.org/contrib/template/precreated/debian-5.0-amd64-minimal.tar.gz


Falls apt-get es nicht automatisch gemacht hat, kann man jetzt OpenVz starten und in den default runlevel legen:

7. /etc/init.d/vz start

8. update-rc.d vz defaults 98

9. Anlegen einer virtuellen Maschiene, a.b.c.d sind durch IP-Adressen zu ersetzten:


vzctl create 101 --ostemplate debian-5.0-amd64-minimal
vzctl set 101 --ipadd a.b.c.d --save
vzctl set 101 --nameserver a.b.c.d --save
vzctl start 101


Nun kann man in sein frisch installiertes System “herabsteigen” und ein Passwort festlegen:

vzctl enter 101
passwd
(Zum beenden der Sitzung dann strg+d drücken)


Und so schnell hat man seine virtuelle Linux-Maschiene lauffähig. Mit vzlist behält man den Überblick über die Maschienen, vzctl stop 101 würde die eben erstelle Maschiene stoppen.
Für weitergehende Konfigurationen kann ich das englisch-sprachige Wiki auf openvz.org empfehlen, vorallem den Teil über user_beancounter sollte man sich gut angucken.

Das wars fürs erste! To be continued!


server1 log # zgrep "Invalid user" /var/log/authlog* | wc
139059 1390590 13655520
server1 log #


Wow, fast 140000 Fehllogins für einen Zeitraum von 42 Tagen. Ungefähr 3000 pro Tag

Wo bliebe der Spaß, wenn man sich nicht auch die Usernames mal (in sortierter Reihenfolge ohne Duplikate) anzeigen lassen kann?


server1 log # zgrep "Invalid user" /var/log/authlog* | awk '{print $8}' | sort | uniq


Unter debian müsste der Befehl so aussehen:

zgrep "invalid user" /var/log/auth.log* | awk '{print $11}' | sort | uniq


Gegebenfalls muss man sich die Spaltennummer (nach dem Dollar) und den Dateinnamen der Authlog anpassen.

Bei mir ergibt das eine lange Liste, die man sich hier runterladen kann.

Na… ist euer Ssh-Account auf der Liste?

Screenshot of extented screen with taskbar

You can clearly see which programs are running and you have a good overview. The other goodies like cpu load display and the clock is also very practical.

The global configuration file /etc/screenrc already has some minor tweaks (Depending on your distribution). If you only want the taskbar for a particular user, than the local .screenrc in your home directory is the file to edit.

The heart of my screen configuration is:


backtick 1 0 0 /usr/bin/cpuusage
hardstatus alwayslastline
hardstatus string '%{= kG} %{G}%H %{g}[%= %{=kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}] %1`%% CPU %{W}%c %{g}’


With “backtick” a command-directive (1 here - must be a number) is noted. The “0 0″ then means that whenever a new output from the program is produced, screen stores the last line of output. “Hardstatus” is for the taskbar and each % directive is for special purposes. With `% 1 for example the last line of the backtick command is printed. For all the other directives better read the GNU screen-manpage

The cpuusage-script looks like this:

1. #!/bin/bash
2. awk ‘BEGIN {file = "/proc/stat";while (a==a) {getline < file;u=$2-up;s=$3-sp;n=$4-np;i=$5-ip;printf ("%2.1f\n"),(u+s)/(u+s+n+i)*100;up=$2;sp=$3;np=$4;ip=$5;close(file);system("sleep 1")}}’
3. Download this code: cpuusage

This awk-oneliner uses the information from /proc/stat to calculate the cpuload for one second. That is supported on all unixes with proc support (Mac OS X has no proc).

What’s missing now, is dynamic window titles. In the previous configuration, all titles are set to “n * bash”, we had to change the titles manually.

With a special escape-sequence, the title can be set from the console. The screen manpage explains the procedure:


The default name for all shell windows can be set with the "shelltitle"
command in the .screenrc file, while all other windows are created with
a "screen" command and thus can have their name set with the -t option.
Interactively, there is the title-string escape-sequence
(kname\) and the “title” command (C-a A). The former can be
output from an application to control the window’s name under software
control, and the latter will prompt for a name when typed. You can
also bind pre-defined names to keys with the “title” command to set
things quickly without prompting.

Finally, screen has a shell-specific heuristic that is enabled by set-
ting the window’s name to “search|name” and arranging to have a null
title escape-sequence output as a part of your prompt. The search por-
tion specifies an end-of-prompt search string, while the name portion
specifies the default shell name for the window. If the name ends in a
‘:’ screen will add what it believes to be the current command running
in the window to the end of the window’s shell name (e.g. “name:cmd”).
Otherwise the current command name supersedes the shell name while it
is running.

Here’s how it works: you must modify your shell prompt to output a
null title-escape-sequence (k\) as a part of your prompt.
The last part of your prompt must be the same as the string you speci-
fied for the search portion of the title. Once this is set up, screen
will use the title-escape-sequence to clear the previous command name
and get ready for the next command. Then, when a newline is received
from the shell, a search is made for the end of the prompt. If found,
it will grab the first word after the matched string and use it as the
command name. If the command name begins with either ‘!’, ‘%’, or ‘^’
screen will use the first word on the following line (if found) in
preference to the just-found name. This helps csh users get better
command names when using job control or history recall commands.

My shellprompt looks like this:


server1 pastacode #


That means, all my commands are typed in after the #. So, I have to add this to my .shellrc :


#dynamic title
shelltitle '# |bash'


Screen now looks for a # when it gets the escape-sequence. “| Bash” means that the default title is “Bash”. We now only need the escape sequence in our promt; that can be customized (in Bash) with the PS1 variable. To do this we will either edit the /etc/bashrc (for any user) or the local .bashrc in our home directory. My .bashrc looks like this:

1. export EDITOR=/usr/bin/vi
2.  
3. # Set the screen title
4. case $TERM in
5. screen*)
6. # This is the escape sequence ESC k \w ESC \
7. #Use path as titel
8. #SCREENTITLE=’\[\ek\w\e\\\]‘
9. #Use program name as titel
10. SCREENTITLE=‘\[\ek\e\\\]‘
11. ;;
12. *)
13. SCREENTITLE=”
14. ;;
15. esac
16.  
17.  
18. PS1="${SCREENTITLE}${PS1}"
19. Download this code: bashrc

The PS1 is altered to add the screen escape-sequence, but only when we are in screen. In my file, you can actually choose between two versions: either the current path is the dynamic title, or the program name, although I prefer the latter. Unfortunately viewing both seems to be not a trivial thing.

So I hope the whole thing works for you - for suggestions, better ideas - write a comment!

Last but not least my complete .screenrc:

1. #no bells and startup messages
2. startup_message off
3. vbell off
4.  
5. #10000 lines scrollback buffer
6. defscrollback 10000
7. #no login
8. deflogin off
9.  
10. # Default shell
11. shell bash
12.  
13. #Timeout for displaying messages
14. msgwait 1
15. activity "         Activity has appeared in window      %n - %t"
16.  
17. #taskbar
18. backtick 1 0 0 /usr/bin/cpuusage
19. hardstatus alwayslastline
20. hardstatus string ‘%{= kG} %{G}%H %{g}[%= %{=kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}] %1`%% CPU %{W}%c %{g}’
21.  
22. #dynamic title
23. shelltitle ‘# |bash’
24.  
25. #When your ssh connection dies, screen is autodetached
26. autodetach on
27.  
28. #Nice 256 term colors
29. attrcolor b ".I"
30. termcapinfo xterm ‘Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm’
31. Download this code: screenrc

And the cpuusage script:

1. #!/bin/bash
2. awk ‘BEGIN {file = "/proc/stat";while (a==a) {getline < file;u=$2-up;s=$3-sp;n=$4-np;i=$5-ip;printf ("%2.1f\n"),(u+s)/(u+s+n+i)*100;up=$2;sp=$3;np=$4;ip=$5;close(file);system("sleep 1")}}’
3. Download this code: cpuusage

Sources:

The pages below helped me alot:

http://listserv.ccjclearline.com/pipermail/kwlug-disc/2006-November/002132.html
http://b79.net/code/screenrc
http://www.mediacollege.com/cgi-bin/man/page.cgi?topic=screen

Songbird screenshot under Mac OS X

Songbird is coming to conquer the crown of this sort of audioplayers. The big download button on getsongbird.com, the domain, the site …. all that is familiar and is reminiscent of Firefox and Co.

Like back then with Firefox, it will take some time until Songbird reaches the masses. I tested it… and hey, I’m really impressed. This player just has the potential to reach the masses. The appearance just seems like iTunes, but there is more to discover under the hood.

Like with Firefox, Songbird can be extended - some interesting plugins have already been developed. There is mashTape that displays all sorts of useful information about the artist played (see screenshot), the Last.fm Album cover plugin, which shows covers from last.fm… or the album art manager, to manage covers locally.

There is even iPod support as plugin, which I have not yet tested. It is a very pleasant thing, to have a free (open source!) audio player as an alternative to Itunes and co.

Long live the birdy!