Thanks, Martin. There must be a script somewhere that is creating
/var/log/dmesg. I can open it and read it with nano. It is ASCII text.
A dmesg.0 file is also created.
Don
>
>> -----Original Message-----
>> From: m("yahoogroups.com","ts-7000");"> [mailto:m("yahoogroups.com","ts-7000");">] On Behalf
>> Of Don Tucker
>> Sent: Friday, May 27, 2011 9:52 AM
>> To: m("yahoogroups.com","ts-7000");">
>> Subject: Re: [ts-7000] stopping logging daemons to reduce SD flash wear
>>
>> I moved S11klogd to K89klogd and S10sysklogd to K90sysklogd, as
>> instructed by the README in /etc/rc2.d. But, that did not seem to work.
>> I tried your suggestion, Jim, and that seemed to stop most of the logs
>> except for dmesg. Thanks! I guess dmesg is OK to keep, since that is
>> just the log of loading the drivers at boot, if I understand correctly.
>> Does anyone know where dmesg gets called? I would like to prevent it
>> from growing too big, if possible.
>>
>
> I am sure I will be corrected if I am wrong .. dmesg is a program that
> lists kernel messages. The kernel messages themselves are not written to
> a file unless you or some other script does this. I think the kernel
> message buffer is a fixed size so old messages get lost.
>
> So there isn't a log called dmesg. On some old systems, there is a script
> that regularly calls
> dmesg -c >> /var/adm/syslog
> so that messages are regularly appended to the syslog, and the buffer
> cleared.
>
> But there isn't a dmesg log as such.
>
> Does this help?
>
> Martin
>
>