On Tuesday 26 May 2009 18:48:01 Ritesh Raj Sarraf wrote: > But why is that? > /proc/kmsg is listed as a regular (0 byte) file. > > -r-------- 1 root root 0 2009-05-26 06:25 /proc/kmsg
Okay!! Looks like /proc/kmsg is the culprit. I sshfs mounted and was able to write to /mount/point/proc/sysrq-trigger successfully, if /proc/kmsg was not being read by cat. /proc/kmsg was being read directly on the server using cat. This way, no hang. Still, is sshfs/fuse still involved for a bug here ? Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
