<p>did u check out syslog feature<br></p>
<p>On 03-May-2012 2:11 PM, "Panagiotis Sakkos" <<a href="mailto:panos.sakkos@cern.ch">panos.sakkos@cern.ch</a>> wrote:<br>
><br>
> Hi again,<br>
><br>
> I would like to ask you the possible ways of logging information from the kernel, without<br>
> the messages being intercepted from dmesg. Also please note that my implementation uses the kprobes API, so in my probes I am atomic and uninterrupted.<br>
><br>
> printk sends the logs to the kernel ring buffer, so dmesg will always see them. Hence, printk-ing is not a solution.<br>
> Logging to a unix socket (i.e. /dev/log) didn't work (check "Crash when sending a lot of messages through a unix socket" thread).<br>
> proc filesystem, I am not sure, but I believe that is not suitable for logging information. It is more for kernel information exposing.<br>
> Any other ideas? My problem is that I log sensitive data and any unprivileged user can run dmesg and see the sensitive logs.<br>
> <br>
> Thank you in advance for your time,<br>
> Panos<br>
> --<br>
> <a href="http://www.cern.ch/psakkos">http://www.cern.ch/psakkos</a><br>
><br>
> _______________________________________________<br>
> Kernelnewbies mailing list<br>
> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
><br>
</p>