OUTPUTD(1X) OUTPUTD(1X)
outputd - capture application output and errors
/usr/lib/desktop/outputd
outputd captures output from applications launched from the desktop (the
file manager, toolchest, session management), and displays them in popup
windows, one per application. If outputd is not running, all output goes
to the system console.
By default, outputd is not launched. It can be launched via the Desktop
customization panel (desktop). This panel can be opened from the Desktop
toolchest by selecting Customize and then Desktop; on the panel, check
the Display Application Errors toggle. Subsequently launched
applications will connect to outputd. Once selected, outputd will
automatically run in subsequent logins. It can be disabled from the
Desktop customization panel as well.
The default mode of outputd is to capture application errors (written to
stderr) in popup windows. Normal output (written to stdout) continues to
go to the console. This behavior can be customized through the use of
resources. Resources should be set by adding a line of the form
outputd*<resourceName>: True (or False)
to your .Xdefaults or .Xresources file.
Any of the following can be used as <resourceName>:
stdoutToWindow
If true, normal application output (stdout) will be sent to a
popup window. If false, it will go to the console. This
defaults to false.
stderrToWindow
If true, application error output (stderr) will be sent to a
popup window. If false, it will go to the console. This
defaults to true.
raiseOnOutput
If true, any normal application output (stdout) will cause the
popup window to raise, even if has been hidden or iconified.
This resource has no effect unless stdoutToWindow is true. This
defaults to false.
raiseOnError
If true, any application error output (stderr) will cause the
popup window to raise, even if has been hidden or iconified.
This resource has no effect unless stderrToWindow is true. This
defaults to true.
Page 1
OUTPUTD(1X) OUTPUTD(1X)
beepOnOutput
If true, any normal application output (stdout) will cause a
beep. This resource has no effect unless stdoutToWindow is true.
This defaults to false.
beepOnError
If true, any application error output (stdout) will cause a beep.
This resource has no effect unless stderrToWindow is true. This
defaults to false.
highlightError
If true, any application error output (stdout) will be
highlighted. This resource has no effect unless stderrToWindow
is true. This option is most useful if both stdoutToWindow and
stderrToWindow are turned on. It allows distinguishing between
error and normal output. This defaults to false.
maxBufferLength
The value of this should be an integer; it is used to determine
how much output (in characters) will be stored per output window
before the initial output is discarded. Setting this low may
lose valuable output. Setting it high will use additional
memory. The default is 10000 characters.
Killing outputd will cause any application that was launched while
outputd was running to die if it tries to produce any output.
If one application is launched from the IRIX Interactive Desktop, and
another application is launched from the first, the title in the outputd
window will show the first application, not the new one. Sometimes this
connection can be obscure. For example, certain daemons, such as
tooltalk, are launched by the first process that needs them. Other
applications using the daemons just connect to them. Any output produced
by the daemon will appear to be from the first process.
outputd is a process. On machines with little memory, it may be better
to avoid running it.
For more information about the entire IRIX Interactive Desktop
environment, see the IID(1) man page.
PPPPaaaaggggeeee 2222 [ Back ]
|
