/etc/system/sysinit has a test:
if ! test /dev/slog -ef /dev/slog; then
slogger
fi
I’d like to give slogger a bigger buffer but slogger is allready running. I
have to kill it first and restart it or spawn a second one unless I can find
(and alter) the lower level script that starts slogger. I have not found it.
Conrad Weyns.
Conrad Weyns <weyns@online.no> wrote:
/etc/system/sysinit has a test:
if ! test /dev/slog -ef /dev/slog; then
slogger
fiI’d like to give slogger a bigger buffer but slogger is allready running. I
have to kill it first and restart it or spawn a second one unless I can find
(and alter) the lower level script that starts slogger. I have not found it.Conrad Weyns.
Slogger is started by diskboot, and I don’t see a way to alter the buffer
size that is used.
Slaying and restarting with the desired buffer size seems to be the
way to go for now.
Peter
Peter Martin <peterm@qnx.com> wrote in message
news:b1min6$d5a$1@nntp.qnx.com…
Conrad Weyns <> weyns@online.no> > wrote:
/etc/system/sysinit has a test:if ! test /dev/slog -ef /dev/slog; then
slogger
fiI’d like to give slogger a bigger buffer but slogger is allready
running. I
have to kill it first and restart it or spawn a second one unless I can
find
(and alter) the lower level script that starts slogger. I have not found
it.Conrad Weyns.
Slogger is started by diskboot, and I don’t see a way to alter the buffer
size that is used.
I thought diskboot have -o option to overwrite any default option ?
But then you need to rebuild the image, which can’t be done on a
NC version of QNX.
Slaying and restarting with the desired buffer size seems to be the
way to go for now.
And put this command in /etc/rc.d/rc.local (create it, chmod a+x it)
would make it automaticly done in every boot
-xtang
“Xiaodan Tang” <xtang@qnx.com> skrev i melding
news:b1mjcu$dtd$1@nntp.qnx.com…
Peter Martin <> peterm@qnx.com> > wrote in message
news:b1min6$d5a$> 1@nntp.qnx.com> …
Conrad Weyns <> weyns@online.no> > wrote:
/etc/system/sysinit has a test:if ! test /dev/slog -ef /dev/slog; then
slogger
fiI’d like to give slogger a bigger buffer but slogger is allready
running. I
have to kill it first and restart it or spawn a second one unless I
can
find
(and alter) the lower level script that starts slogger. I have not
found
it.Conrad Weyns.
Slogger is started by diskboot, and I don’t see a way to alter the
buffer
size that is used.I thought diskboot have -o option to overwrite any default option ?
But then you need to rebuild the image, which can’t be done on a
NC version of QNX.Slaying and restarting with the desired buffer size seems to be the
way to go for now.And put this command in /etc/rc.d/rc.local (create it, chmod a+x it)
would make it automaticly done in every boot-xtang
Thanks to both of you for clearing this up. It’s unfortunate to have to slay
it because then I loose that loginfo. On the other hand, it lookes like I
can simply start a new slogger. It will take over any future logging. After
slaying it, the old one (started by diskboot) becomes viewable with
sloginfo.
(For a newbie as I am, loginfo of any kind is vital to understanding why
something isn’t working as expected)
Conrad
If you worried about “old logs”, then store it somewhere:
sloginfo > /dev/shmem/oldlog
slay slogger
slogger -s
-xtang
Conrad Weyns <weyns@online.no> wrote in message
news:b1nrg6$6vo$1@inn.qnx.com…
“Xiaodan Tang” <> xtang@qnx.com> > skrev i melding
news:b1mjcu$dtd$> 1@nntp.qnx.com> …
Peter Martin <> peterm@qnx.com> > wrote in message
news:b1min6$d5a$> 1@nntp.qnx.com> …
Conrad Weyns <> weyns@online.no> > wrote:
/etc/system/sysinit has a test:if ! test /dev/slog -ef /dev/slog; then
slogger
fiI’d like to give slogger a bigger buffer but slogger is allready
running. I
have to kill it first and restart it or spawn a second one unless I
can
find
(and alter) the lower level script that starts slogger. I have not
found
it.Conrad Weyns.
Slogger is started by diskboot, and I don’t see a way to alter the
buffer
size that is used.I thought diskboot have -o option to overwrite any default option ?
But then you need to rebuild the image, which can’t be done on a
NC version of QNX.Slaying and restarting with the desired buffer size seems to be the
way to go for now.And put this command in /etc/rc.d/rc.local (create it, chmod a+x it)
would make it automaticly done in every boot-xtang
Thanks to both of you for clearing this up. It’s unfortunate to have to
slay
it because then I loose that loginfo. On the other hand, it lookes like I
can simply start a new slogger. It will take over any future logging.
After
slaying it, the old one (started by diskboot) becomes viewable with
sloginfo.(For a newbie as I am, loginfo of any kind is vital to understanding why
something isn’t working as expected)Conrad
\
“Xiaodan Tang” <xtang@qnx.com> skrev i melding
news:b1oivr$nd6$1@nntp.qnx.com…
If you worried about “old logs”, then store it somewhere:
sloginfo > /dev/shmem/oldlog
slay slogger
slogger -s <big buffer
Thanks!
conrad.
-xtang
Conrad Weyns <> weyns@online.no> > wrote in message
news:b1nrg6$6vo$> 1@inn.qnx.com> …“Xiaodan Tang” <> xtang@qnx.com> > skrev i melding
news:b1mjcu$dtd$> 1@nntp.qnx.com> …
Peter Martin <> peterm@qnx.com> > wrote in message
news:b1min6$d5a$> 1@nntp.qnx.com> …
Conrad Weyns <> weyns@online.no> > wrote:
/etc/system/sysinit has a test:if ! test /dev/slog -ef /dev/slog; then
slogger
fiI’d like to give slogger a bigger buffer but slogger is allready
running. I
have to kill it first and restart it or spawn a second one unless
I
can
find
(and alter) the lower level script that starts slogger. I have not
found
it.Conrad Weyns.
Slogger is started by diskboot, and I don’t see a way to alter the
buffer
size that is used.I thought diskboot have -o option to overwrite any default option ?
But then you need to rebuild the image, which can’t be done on a
NC version of QNX.Slaying and restarting with the desired buffer size seems to be the
way to go for now.And put this command in /etc/rc.d/rc.local (create it, chmod a+x it)
would make it automaticly done in every boot-xtang
Thanks to both of you for clearing this up. It’s unfortunate to have to
slay
it because then I loose that loginfo. On the other hand, it lookes like
I
can simply start a new slogger. It will take over any future logging.
After
slaying it, the old one (started by diskboot) becomes viewable with
sloginfo.(For a newbie as I am, loginfo of any kind is vital to understanding why
something isn’t working as expected)Conrad
\