It is possible to reconfigure slogger so that it writes the system log to a
specific section of RAM? In particular, I have some battery-backed RAM where
I’d like the log to go so I can view the results after a reboot.
Cheers,
Randy Hyde
Randall Hyde <randall.nospam.hyde@ustraffic.net> wrote:
It is possible to reconfigure slogger so that it writes the system log to a
specific section of RAM? In particular, I have some battery-backed RAM where
I’d like the log to go so I can view the results after a reboot.
Not that I know of – but you could write a simple resource manager
that handles write messages, and writes the data to that area of
battery-backed RAM (including handling wrapping of the buffer, etc),
and redirect slogger to the device that your resource manager registers.
The resource manager side of things is pretty easy – I expect you’d
only have to handle the write() message, the memory buffer management
wouldn’t be too difficult either, I expect.
-David
QNX Training Services
http://www.qnx.com/services/training/
Please followup in this newsgroup if you have further questions.
How about creating a filesystem in the battery backed RAM using
devf-ram, then direct slogger to write it files there?
- Dan
David Gibbs wrote:
Randall Hyde <> randall.nospam.hyde@ustraffic.net> > wrote:
It is possible to reconfigure slogger so that it writes the system log to a
specific section of RAM? In particular, I have some battery-backed RAM where
I’d like the log to go so I can view the results after a reboot.
Not that I know of – but you could write a simple resource manager
that handles write messages, and writes the data to that area of
battery-backed RAM (including handling wrapping of the buffer, etc),
and redirect slogger to the device that your resource manager registers.The resource manager side of things is pretty easy – I expect you’d
only have to handle the write() message, the memory buffer management
wouldn’t be too difficult either, I expect.-David
Dan Giorgis <dang@tridium.com> wrote:
How about creating a filesystem in the battery backed RAM using
devf-ram, then direct slogger to write it files there?
Hm… have to make sure devf-ram will take the right RAM, rather
than just allocating some. The -s baseaddress might work, haven’t
tried it. This will, also, make far less efficient use of the
RAM, that is, there will be a lot more overhead in filesystem
type information there, as it creates a “flash” filesystem in
that area, with all the effects thereof. Small writes are,
especially, expensive – and that’s what you’ll usually get from
slogger, I expect.
-David
Not that I know of – but you could write a simple resource manager
that handles write messages, and writes the data to that area of
battery-backed RAM (including handling wrapping of the buffer, etc),
and redirect slogger to the device that your resource manager registers.The resource manager side of things is pretty easy – I expect you’d
only have to handle the write() message, the memory buffer management
wouldn’t be too difficult either, I expect.-David
–
QNX Training Services
http://www.qnx.com/services/training/
Please followup in this newsgroup if you have further questions.