gpg: failed to create temporary file '/var/lib/lurker/.#lk0x58164100.hantslug.org.uk.23593': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Sat Jul 21 05:40:26 2007 BST
gpg: using DSA key 2099B64CBF15490B
gpg: Can't check signature: No public key
Hi,
I've got 3 servers, two of which are on etch and one is still on
sarge. All three have their serial ports connected to a Cisco
terminal server. Recently I've been trying to use the magic sysrq
commands[1] over serial and I find that I can't trigger them on the
etch servers.
Normally to trigger a sysrq command you would send a serial break
followed by (within 5 seconds) the command key. On these terminal
servers it is ctrl-^,b (control+shift+6 followed by b), and indeed
on the sarge server doing ctrl+shift+6,b,h prints the sysrq help
line.
I've checked the obvious things:
- all three servers have sysrq enabled as confirmed by:
$ cat /proc/sys/kernel/sysrq
1
- the ones that don't work by serial do work if the command is
echoed to the trigger file
- the terminal server configuration is identical, break characters
are the same, and breaks are being sent
I am not sure if sysrq ever worked on those two machines.
The only thing I haven't tested, and will if I haven't sorted this
out by the next time I visit the datacentre, is to plug a serial
cable from my laptop directly in and do it with minicom.
Any other ideas?
Cheers,
Andy
[1]
http://snafu.freedom.org/linux2.2/docs/sysrq.txt
