10-08-2007
You would need to use C or something like that. This is beyond what I want want to try via a script. perl could handle it though. basicly you will need to allocate a psuedo tty and arrange for the user to interact with the pty. Your program would sit between the user's "real" tty and the psuedo tty you allocate. The program called "script" does all of this, not to translate, but to capture all input and output to a file. So you could obtain the source code to script and study that as a starting point.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I need to redirect stdout and stderr to a file in a ksh shell. That's not a problem. But I need also the correct exit code for the executed command. In the example below I redirect correctly the stdout & stderr to a file, but I have the exit code of tee command and not for the mv... (2 Replies)
Discussion started by: up69
2 Replies
2. Shell Programming and Scripting
In bash, I need to send the STDOUT and STDERR from a command to one file, and then just STDERR to another file. Doing one or the other using redirects is easy, but trying to do both at once is a bit tricky. Anyone have any ideas? (9 Replies)
Discussion started by: jshinaman
9 Replies
3. UNIX for Advanced & Expert Users
Hello Everyone!
I'm trying to combine output for standard output and for possible standard error to the log file. I was trying to use tee command, but it turned out if error occurred error output will be send to the screen only and will not be redirected with tee command to the log file.
Anyone... (11 Replies)
Discussion started by: slavam
11 Replies
4. Shell Programming and Scripting
Friends
I have to redirect STDERR messages both to screen and also capture the same in a file.
2 > &1 | tee file works but it also displays the non error messages to file, while i only need error messages.
Can anyone help?? (10 Replies)
Discussion started by: vikashtulsiyan
10 Replies
5. Shell Programming and Scripting
Hello Friends,
sorry, i am not very familiar with Unix programming. Could you please help me on this?
We have to start different components from a startup script.
each components are started as below in the background in a startprocess function
$nohup $file $args >>$logFile 2>&1 &
... (0 Replies)
Discussion started by: alvinbush
0 Replies
6. Solaris
Hello Friends,
sorry, i am not very familiar with Unix programming. Could you please help me on this?
We have to start different components from a startup script.
each components are started as below in the background in a startprocess function
$nohup $file $args >>$logFile 2>&1 &
... (1 Reply)
Discussion started by: alvinbush
1 Replies
7. Shell Programming and Scripting
Currently I am redirecting STDERR and STDOUT to a log file by doing the following
{
My KSH script contents
} 2>&1 | $DEBUGLOG
Problem is the STDERR & STDOUT do not have any date/time associated.
I want this to be something that i can embed into a script opposed to an argument I use... (4 Replies)
Discussion started by: nitrobass24
4 Replies
8. Shell Programming and Scripting
Dear all,
redirecting STDOUT & STDERR to file is quite simple, I'm currently using:
exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that?
Thanks
Lucas (4 Replies)
Discussion started by: Lord Spectre
4 Replies
9. Shell Programming and Scripting
Hi folks
I need/want to redirect output (stdout, stderr) from an exec call to separate files. One for stderr only and two(!) different (!) ones for the combined output of stderr and stdout.
After some research and testing i got this so far :
(( exec ${command} ${command_parameters} 3>&1... (6 Replies)
Discussion started by: MDominok
6 Replies
10. Shell Programming and Scripting
Dear all,
redirecting STDOUT & STDERR to file is quite simple, I'm currently using:
Code:
exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log
But during script execution I would like the output come back again to screen, how to do that?
Thanks
Luc
edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies
LEARN ABOUT DEBIAN
roarclientpass
roarclientpass(1) System User's Manual: roarclientpass roarclientpass(1)
NAME
roarclientpass - Passing clients to and creating new listen sockets on RoarAudio sound server
SYNOPSIS
roarclientpass [OPTIONS]...
DESCRIPTION
This program let you pass new clients to a RoarAudio sound server as as a proxy and let you add new listen sockets to a running server.
OPTIONS
--server SERVER
Set server hostname.
--stdin
Client is on stdin.
--stdout
Client is on stdout.
--stdio
Same as --stdin --stdout.
This option may for example be used in case of being runed from a inetd.
--stderr
Client is on stderr.
Beside to make stderr known as client fh it will disable error output on stderr. This must be used in case this program is used
from inetd or simular tools.
--client-fh FH
Client is on FH.
This is basicly the same as --client-fh on roard(1).
--proto PROTO
Set the protocol used by the client.
Defaults to RoarAudio.
--byteorder BO
Sets the byteorder used by the client.
Defaults to network byte order.
--listen
Client is a listen connection.
This is not the same as --mode listen.
--mode MODE
Set mode of operation: none, listen or connect
Defaults to none.
--bind BIND
Set host/node/path for mode listen and connect.
--port PORT
Set port for mode listen and connect.
--help Show this help
SEE ALSO
roartips(7), libroar(7), RoarAudio(7).
HISTORY
For history information see RoarAudio(7).
RoarAudio July 2010 roarclientpass(1)