<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Toggling xterm logging in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115226#M897650</link>
    <description>well, specifically in the case of a dtterm, it has the default action for all signals.  The default action is to terminate so I guess there isn't much you can do apart from the suggestions above.</description>
    <pubDate>Tue, 11 Nov 2003 06:30:56 GMT</pubDate>
    <dc:creator>Mark Grant</dc:creator>
    <dc:date>2003-11-11T06:30:56Z</dc:date>
    <item>
      <title>Toggling xterm logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115223#M897647</link>
      <description>Hello All,&lt;BR /&gt;&lt;BR /&gt;I have an application that is running in, and writes to the stdout of an xterm window.  I need to create a log of the output from the application.&lt;BR /&gt;&lt;BR /&gt;I am aware that after the application has started, one can enable or disable logging via a mouse click by selecting or deselecting the "log to file" option in the pop down menu.&lt;BR /&gt;&lt;BR /&gt;However, this requires one to have access to the xterm window itself.  If I am diailing in via a modem into the machine where my application is already running in an xterm window, is there anay way that I can send a message from the command line that essentially does the same thing as toggling the "log to file" menu item?&lt;BR /&gt;&lt;BR /&gt;I am running HP-UX B.10.20 on a 9000/820 series machine.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Raj&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Nov 2003 13:14:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115223#M897647</guid>
      <dc:creator>Raj Kotaru</dc:creator>
      <dc:date>2003-11-10T13:14:30Z</dc:date>
    </item>
    <item>
      <title>Re: Toggling xterm logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115224#M897648</link>
      <description>Are you really running xterm, or is it some other emulator (eg hpterm, dtterm).&lt;BR /&gt;&lt;BR /&gt;I ask because I don't think xterm has logging capability (not on my machine and not in the man page), whereas hpterm and dtterm do.&lt;BR /&gt;&lt;BR /&gt;If hpterm or dtterm, why not just start up logging at invocation time (using "-l -lf logfile") and leave it on ?&lt;BR /&gt;&lt;BR /&gt;-- Graham</description>
      <pubDate>Tue, 11 Nov 2003 05:30:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115224#M897648</guid>
      <dc:creator>Graham Cameron_1</dc:creator>
      <dc:date>2003-11-11T05:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: Toggling xterm logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115225#M897649</link>
      <description>I have seen ways in the past, but if they still work, it is a security issue...&lt;BR /&gt;&lt;BR /&gt;But it depends on what you want. A way that works is using xwd... You can dump the contents of the hpterm at the time you want the contents. But to get info over a period of time, this will not work.</description>
      <pubDate>Tue, 11 Nov 2003 06:27:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115225#M897649</guid>
      <dc:creator>Elmar P. Kolkman</dc:creator>
      <dc:date>2003-11-11T06:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: Toggling xterm logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115226#M897650</link>
      <description>well, specifically in the case of a dtterm, it has the default action for all signals.  The default action is to terminate so I guess there isn't much you can do apart from the suggestions above.</description>
      <pubDate>Tue, 11 Nov 2003 06:30:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115226#M897650</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-11-11T06:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: Toggling xterm logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115227#M897651</link>
      <description>xterm logging has been disabled by and large by most vendors. &lt;BR /&gt;&lt;BR /&gt;A better solution would be to modify the command that is running in the xterm window to use the tee command and log all of the application output to a file that you can examine remotely.&lt;BR /&gt;You might have to dig around through the apps startup scripts to achieve this.   Another optio n might be to modify the application script to use typescript.</description>
      <pubDate>Tue, 11 Nov 2003 09:09:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115227#M897651</guid>
      <dc:creator>Rick Beldin</dc:creator>
      <dc:date>2003-11-11T09:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: Toggling xterm logging</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115228#M897652</link>
      <description>Thanks to all those who responded.  I did finally find a way to do this.&lt;BR /&gt;&lt;BR /&gt;I used the -lf option to xterm to specify a logfile, except that instead of specifying an actual file name, I specified the endpoint of a pipeline.  This can be a shell script to which the output from the xterm window would be piped as input.  I wrote the script in the korn shell to utlize the ability to handle signals sent to the script.  I used the SIGUSR1 signal to specify to the shell script that its input needs to be logged, and the SIGUSR2 signal to specify that its input no longer needs to be logged.  &lt;BR /&gt;&lt;BR /&gt;To send the signals, I used the "kill" command.  For example, "kill -SIGUSR1 pid", where pid is the process id of my korn shell script.  This seems to work.  &lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Raj&lt;BR /&gt;</description>
      <pubDate>Tue, 11 Nov 2003 11:24:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toggling-xterm-logging/m-p/3115228#M897652</guid>
      <dc:creator>Raj Kotaru</dc:creator>
      <dc:date>2003-11-11T11:24:43Z</dc:date>
    </item>
  </channel>
</rss>

