Logging information through printk

[Alex Iribarren <alex dot iribarren dot lists at gmail dot com>]

Hi,

I've written a systemtap script that tracks network connections and logs
data about them. I'm using printk to log the data, but this is causing
kernel panics when there are a lot of connections.

I see from bugzilla
(http://sourceware.org/bugzilla/show_bug.cgi?id=3541) that these kind of
problems are known, but I don't see anything in the way of a workaround.
One solution is to use system("/usr/bin/logger blabla") instead of
printk, but then I'm afraid I'll be forking too many processes and
creating lots of extra overhead.

Can you guys suggest another alternative? Is there a safe way of calling
printk?

Cheers,
Alex

Attachment: signature.asc
Description: OpenPGP digital signature