capturar la consola serie de otro server
Gente, esta vez vengo con algo un poco mas importante que unos caracteres mal dibujados.. la tarea serìa, porder capturar desde un linux, el output de la consola serie de otro linux, pero todo esto, sin instalar cu, kermit, etc. (esto es por un tema de licencias de una aplicaciòn de este server) hasta ahora, lo que intentè fuè, del syslog, redirigir todos los eventos a /dev/ttyS0, y del otro lado, ejecuto tail -f /dev/ttyS0 si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio Saludos!
On Wed, 06 Sep 2006 13:27:20 -0300 ricardo <ricardo.valiente@gmail.com> wrote:
hasta ahora, lo que intentè fuè, del syslog, redirigir todos los eventos a /dev/ttyS0, y del otro lado, ejecuto tail -f /dev/ttyS0 si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio SCRIPT(1) System General Commands Manual SCRIPT(1)
NAME script - make typescript of terminal session SYNOPSIS script [-a] [-c COMMAND] [-f] [-q] [-t] [file] DESCRIPTION Script makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1). If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript. Options: Salu2, luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.mannucci.ORG/
Luciano Mannucci wrote:
On Wed, 06 Sep 2006 13:27:20 -0300 ricardo <ricardo.valiente@gmail.com> wrote:
si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me). Damon Register
Damon Register wrote:
Luciano Mannucci wrote:
On Wed, 06 Sep 2006 13:27:20 -0300 ricardo <ricardo.valiente@gmail.com> wrote:
si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me).
Damon Register
ok, thanks, I sooo sorry (I hope this language match to you) the big thing is: Capture in a Linux box, the output of the serial console of another one Linux, but without installing cu, kermit, etc. (this is by a subject of the application license of this appliance) till now, I have try to configure in syslog, redir all the events to /dev/ttyS0, and execute "tail - f /dev/ttyS0" in the other side, yeah, this attempt is almost primitive, but I haven't no idea how to do this.
Wed, 06 Sep 2006, by ricardo.valiente@gmail.com:
Damon Register wrote:
Luciano Mannucci wrote:
On Wed, 06 Sep 2006 13:27:20 -0300 ricardo <ricardo.valiente@gmail.com> wrote:
si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me).
Damon Register
ok, thanks, I sooo sorry (I hope this language match to you) the big thing is: Capture in a Linux box, the output of the serial console of another one Linux, but without installing cu, kermit, etc. (this is by a subject of the application license of this appliance) till now, I have try to configure in syslog, redir all the events to /dev/ttyS0, and execute "tail - f /dev/ttyS0" in the other side, yeah, this attempt is almost primitive, but I haven't no idea how to do this.
Maybe: http://freshmeat.net/projects/serialoverip/ ? Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
Theo v. Werkhoven wrote:
Wed, 06 Sep 2006, by ricardo.valiente@gmail.com:
Damon Register wrote:
Luciano Mannucci wrote:
On Wed, 06 Sep 2006 13:27:20 -0300 ricardo <ricardo.valiente@gmail.com> wrote:
si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio
SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me).
Damon Register
ok, thanks, I sooo sorry (I hope this language match to you) the big thing is: Capture in a Linux box, the output of the serial console of another one Linux, but without installing cu, kermit, etc. (this is by a subject of the application license of this appliance) till now, I have try to configure in syslog, redir all the events to /dev/ttyS0, and execute "tail - f /dev/ttyS0" in the other side, yeah, this attempt is almost primitive, but I haven't no idea how to do this.
Maybe: http://freshmeat.net/projects/serialoverip/ ?
Theo
nop, I have connected this linux via the serial ports.
si, es casi primitiva la prueba, pero como no se me ocurriò nada mas inteligente, pregunto por si me pudiesen ayudar con algo mas serio
SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me).
Damon Register
ok, thanks, I sooo sorry (I hope this language match to you) the big thing is: Capture in a Linux box, the output of the serial console of another one Linux, but without installing cu, kermit, etc. (this is by a subject of the application license of this appliance) till now, I have try to configure in syslog, redir all the events to /dev/ttyS0, and execute "tail - f /dev/ttyS0" in the other side, yeah, this attempt is almost primitive, but I haven't no idea how to do this.
nop, I have connected this linux via the serial ports.
I did not fully understand the original post, though. screen can connect to a serial port and at the same time log it (as does minicom), script is really just a wrapper around your current tty, and there is also e.g. ttyrpld for kernel-level tty monitoring. Last but not least, you can also manually play with inb or open(/dev/ttyS0). Jan Engelhardt --
> si, es casi primitiva la prueba, pero como no se me ocurriò nada mas > inteligente, pregunto por si me pudiesen ayudar con algo mas serio > > SCRIPT(1) System General Commands Manual SCRIPT(1)
Cool. Not only a useful response instead of a flame for incorrect language but also I learned something I didn't know before. The only bad thing is the characters are not coming through correctly (at least for me).
Damon Register
ok, thanks, I sooo sorry (I hope this language match to you) the big thing is: Capture in a Linux box, the output of the serial console of another one Linux, but without installing cu, kermit, etc. (this is by a subject of the application license of this appliance) till now, I have try to configure in syslog, redir all the events to /dev/ttyS0, and execute "tail - f /dev/ttyS0" in the other side, yeah, this attempt is almost primitive, but I haven't no idea how to do this.
nop, I have connected this linux via the serial ports.
I did not fully understand the original post, though. screen can connect to a serial port and at the same time log it (as does minicom), script is really just a wrapper around your current tty, and there is also e.g. ttyrpld for kernel-level tty monitoring. Last but not least, you can also manually play with inb or open(/dev/ttyS0).
Jan Engelhardt -- ok, I try to explain in other way: I have an appliance, whit a serial port/console, and I have to set a
Jan Engelhardt wrote: linux box (with the limitation to install any software ej:cu, kermit, etc) to connect via serial to the appliance. And the point is "How to capture the output of the console of the appliance?" (this is for just in case the box crashes) I have the permission to put and run any script (if necessary), in the linux monitor to do this.
I did not fully understand the original post, though. screen can connect to a serial port and at the same time log it (as does minicom), script is really just a wrapper around your current tty, and there is also e.g. ttyrpld for kernel-level tty monitoring. Last but not least, you can also manually play with inb or open(/dev/ttyS0).
ok, I try to explain in other way: I have an appliance, whit a serial port/console, and I have to set [up] a linux box (with the limitation to install any software ej:cu, kermit, etc) to connect via serial to the appliance.
"Limitation to install"? Allowed to install something or not allowed? Note that you can always "install" (read: put some binaries) into your home directory and run them from there.
And the point is "How to capture the output of the console of the appliance?" (this is for just in case the box crashes)
See above. screen/script/minicom/ttyrpld can do that, using various techniques at different levels. I am not sure if kermit includes a built-in logging facility.
I have the permission to put and run any script (if necessary), in the linux monitor to do this.
All except ttyrpld do not require any kernel modification (the latter serves a special purpose though) and should therefore be easy-to-use. Besides the program, only permission on /dev/ttyS0 is needed, so you can run it with an unprivileged user account, or even a chroot. Jan Engelhardt --
Jan Engelhardt wrote:
I did not fully understand the original post, though. screen can connect to a serial port and at the same time log it (as does minicom), script is really just a wrapper around your current tty, and there is also e.g. ttyrpld for kernel-level tty monitoring. Last but not least, you can also manually play with inb or open(/dev/ttyS0).
ok, I try to explain in other way: I have an appliance, whit a serial port/console, and I have to set [up] a linux box (with the limitation to install any software ej:cu, kermit, etc) to connect via serial to the appliance.
"Limitation to install"? Allowed to install something or not allowed? Note that you can always "install" (read: put some binaries) into your home directory and run them from there.
The appliance, and the linux box are licensed, so I have a contract with my service support that limit to me.
And the point is "How to capture the output of the console of the appliance?" (this is for just in case the box crashes)
See above. screen/script/minicom/ttyrpld can do that, using various techniques at different levels. I am not sure if kermit includes a built-in logging facility.
I have the permission to put and run any script (if necessary), in the linux monitor to do this.
All except ttyrpld do not require any kernel modification (the latter serves a special purpose though) and should therefore be easy-to-use. Besides the program, only permission on /dev/ttyS0 is needed, so you can run it with an unprivileged user account, or even a chroot.
OK, many thanks
Jan Engelhardt
participants (5)
-
Damon Register -
Jan Engelhardt -
Luciano Mannucci -
ricardo -
Theo v. Werkhoven