Wait a minute! I just realised that after starting urxvtd it really does run, although it gives that error message I told you about. After that I can open new urxvt-windows with command urxvtc .
Maybe the problem is this: urxvtd tries to behave like option -m was used, no matter if it really was used. Then it fails to lock itself to RAM, but it do not exit. It just goes on working, but without locking itself to RAM. -- Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv "Quidquid Latine dictum sit altum videtur." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
