AIXThis forum is for the discussion of IBM AIX.
eserver and other IBM related questions are also on topic.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I need a way of logging all output to the screen on AIX for logging telnet sessions. I've been using the script command but the problem I found with this is that there is some sort of buffer that is filled before the data is written to a file and if the telnet session is terminated abruptly, so is th script command, and I lose a considerable amount of data. If the session is ended properly, with an exit command, then everything works well.
Is there any other way of doing the logging that I want? I'd even be willing to manually edit the script command if I had the source code.
You might want to telnet in, start "screen" THEN start "script". The "screen" command allows you to attach and detach from a session even on different terminals. If your session aborts you should be able to log back in and reattach to the "screen" session.
"screen" like "script" is a program you'd likely have to download.
One caveat - "screen" has its own hot keys like "script" does. I recall doing "screen" and "script" together on HP at a prior job but seem to recall having had to play with the hot keys because they had one in common.
The dscreen command starts the Dynamic Screen utility, which allows a single
physical terminal to be connected to several virtual sessions, or screens, at
If no flags are specified, the dscreen command reads the description for the
terminal specified in the TERM environment variable from the file specified in
the DSINFO environment variable. If the DSINFO environment variable is not
specified, the terminal description is read from the /etc/dsinfo file. A
terminal description typically contains the following configuration information:
o Keys used with the Dynamic Screen utility and their function
o Number of pages of screen memory the terminal has available
o Code sequences that must be sent or received to access and use Dynamic
We have about 15 AIX boxes, they run an application which is served out to our clients. Every so often, the software vendor will need to telnet into the servers and make whatever changes they need to do. A few times, they have been logged in and some change they did cause some downtime. I was given the task of figuring out how to the telnet session. I want to log all input, and output to the display.