Yes, "<0>my message here\n" really works. It gets printed on the remote
terminal as well. However, it does have a side effect. The speaker beeps
with each line of output and inserts another line "Message from
syslog@mymachine at Thu Apr 5 01:04:30 2001 ..." between each line of
output. It looks (and sounds) like one of those broadcast messages that
operators send to users before shutting down.
Nevertheless, it does work, and I might just disable my speaker. I have
not yet tried Eric Peterson's suggestion (man klogd(8)). I am indeed
grateful for all the responses on this question.
Ollie Enders
"Basham, Richard R" <[EMAIL PROTECTED]> on 04/05/2001 08:55:14
AM
To: "Kalyanaraman, Sivakumar (CTS)" <[EMAIL PROTECTED]>,
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: RE: [rtl] print_rtl during remote login
I borrowed a piece of code a while back and here is one thing that I saw.
printk("<0>my message here\n");
I changed it to
rtl_printf("<0>my message here\n:);
and in both cases the message was broadcast to all open windows and also
logged to be viewed by dmesg.
I do not know how this performs when remotely logged in.
I don't know why this works this way but it could be useful.
Rich
> ----------
> From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 30, 2001 10:50 AM
> To: Kalyanaraman, Sivakumar (CTS)
> Cc: [EMAIL PROTECTED]
> Subject: RE: [rtl] print_rtl during remote login
>
> <<File: InterScan_Disclaimer.txt>>
>
>
> Hi Siva,
>
> Typing dmesg at the remote terminal does allow viewing of the kernel ring
> buffer on the other machine. It does what I want, although it would be
> nice if you didn't have to type dmesg all the time. Probably the only
> other way to get the print messages out of the rtl module is through a
> fifo?
>
> Thanks very much
> Ollie
>
>
>
>
>
>
> "Kalyanaraman, Sivakumar (CTS)" <[EMAIL PROTECTED]> on 03/29/2001
> 10:59:45 PM
>
> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> cc: 'rtl' <[EMAIL PROTECTED]>
> Subject: RE: [rtl] print_rtl during remote login
>
>
>
>
> Hi,
> if my understanding is correct, rtl_printf messages go directly
to
> the console of the system. to view these messages, you can use dmesg so
> that all the logged messages can be seen from the remote terminal.
>
> regards,
> siva
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, March 29, 2001 10:47 PM
> > To: [EMAIL PROTECTED]
> > Subject: [rtl] print_rtl during remote login
> >
> >
> > When I operate my rtlinux machine remotely using rlogin from another
> > machine, the printf_rtl output from within my program goes to
> > the screen of
> > the rtlinux machine instead of to the remote machine. This behavior
> > applies not just to my output but also to other rtl messages such as
> > "RTLinux Extensions Loaded (http://www.fsmlabs.com/)".
> >
> > But regular operating system messages, including the gdb
> > debugger messages,
> > do go over to the remote machine as expected.
> >
> > Is there a mechanism for redirecting the standard output?
> >
> > This seems like an important capability that probably has an
> > easy answer.
> >
> > Thanks
> > Ollie
> >
> >
> > -- [rtl] ---
> > To unsubscribe:
> > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> > echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> > --
> > For more information on Real-Time Linux see:
> > http://www.rtlinux.org/rtlinux/
> >
>
> (See attached file: InterScan_Disclaimer.txt)
>
>
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
