Comment 22 for bug 81227

On Wed, 2007-03-14 at 07:46 +0000, jens_acamedia wrote:
> why does
> "lshal -m > file"
> not work

I wondered this myself, and have no explanation. I suppose - and this is
a guess - the lshal dev chose to directly manipulate streams when lshal
is invoked with --monitor (-m) to prevent lshal itself from disturbing
the devices it is monitoring....

> i cant capture it unless its piped to a file since my computer
> shuts down when i press powerbutton. help appreciated..thanks

Try using script:

$ script halout
$ lshal -m

Then, whatever happens, halout should contain what you are looking for
(probably best not to write the script file - halout - to /tmp, it could
cleaned away reboot). For best results, you might try

script -f -c "lshal -m" halout

That puts the whole thing on one line, and the -f option ensures that
output is flushed to disk as it is produced.