Herez the question,
In a process which writes into file FILE1 with descriptor
fHandler1 and it is run as a background process
where would statements be directed
when stderr descriptor is used.
fprintf(stderr,"some message\n");
assume that session from which it is run is terminated and... (3 Replies)
Hi,
Need some help here on a script I'm writing. I know that STDERR is normally done is this manner:
script 2>stderr.out
However, if I wanted to output the stderr from a rsh command how do I do that?
Example:
su - username -c "rsh $hostname /opt/gilberteu/scriptname" 1>stdout... (5 Replies)
Hi there,
I was wondering if it was possible to pipe stderr to another process.
I need to eval commands given as arguments and I would like to redirect stderr to another process.
I can redirect stderr to a file like this...
toto:~$ command="one=1"
toto:~$ eval $command 2> error
toto:~$... (5 Replies)
Can somebody explain to me why the diff output is not going to stderr?
Yet when I issue a diff from the command line the return code is -ne 1.
I am guessing diff always writes to stdout???
Is there away I can force the difff to write to stderr USING THE CURRENT
template. If possible, I... (5 Replies)
Hello
I try to store stderr into a variable, then if this var is not empty i send an email and stop my script.
I think my problem is due of "<$dump" into my command line.
my bad command line (see samples below on this post)
if ! $returnedStr ;
then
echo ERROR READING DUMP: ... (8 Replies)
Hi Experts,
i have a solaris 9 OS and i get the following message repeated many time in my /var/adm/messages :
Oct 31 16:30:44 baobab rsh: can't get stderr port: Cannot assign requested address
have you any idea how can i resolve this issue ??:confused:
thanks for help (2 Replies)
Hello,
Can you please if the bellow is the proper way of appending a variable to the stderr:
The easiest way to test this,I was able to imagine, was by touching 5 files and afterwards looping trough to the results:
-rw-r--r-- 1 ab owner 0 Sep 14 13:45 file1
-rw-r--r-- 1 ab owner 0 Sep... (7 Replies)
Hi All,
I am writing a shell script code. and i want the stderr to be send to a file and the stdout to be displayed in terminal. In my shell script code i use a read command to get data from user.read -r -p "Enter the type :" data
and while i execute my script i use./my_script.sh 2>... (4 Replies)
Discussion started by: Vinoth R
4 Replies
LEARN ABOUT MOJAVE
code
code(n) [incr Tcl] code(n)
__________________________________________________________________________________________________________________________________________________NAME
code - capture the namespace context for a code fragment
SYNOPSIS
itcl::code ?-namespace name? command ?arg arg ...?
_________________________________________________________________DESCRIPTION
Creates a scoped value for the specified command and its associated arg arguments. A scoped value is a list with three elements: the
"@scope" keyword, a namespace context, and a value string. For example, the command
namespace foo {
code puts "Hello World!"
}
produces the scoped value:
@scope ::foo {puts {Hello World!}}
Note that the code command captures the current namespace context. If the -namespace flag is specified, then the current context is
ignored, and the name string is used as the namespace context.
Extensions like Tk execute ordinary code fragments in the global namespace. A scoped value captures a code fragment together with its
namespace context in a way that allows it to be executed properly later. It is needed, for example, to wrap up code fragments when a Tk
widget is used within a namespace:
namespace foo {
private proc report {mesg} {
puts "click: $mesg"
}
button .b1 -text "Push Me" -command [code report "Hello World!"]
pack .b1
}
The code fragment associated with button .b1 only makes sense in the context of namespace "foo". Furthermore, the "report" procedure is
private, and can only be accessed within that namespace. The code command wraps up the code fragment in a way that allows it to be exe-
cuted properly when the button is pressed.
Also, note that the code command preserves the integrity of arguments on the command line. This makes it a natural replacement for the
list command, which is often used to format Tcl code fragments. In other words, instead of using the list command like this:
after 1000 [list puts "Hello $name!"]
use the code command like this:
after 1000 [code puts "Hello $name!"]
This not only formats the command correctly, but also captures its namespace context.
Scoped commands can be invoked like ordinary code fragments, with or without the eval command. For example, the following statements work
properly:
set cmd {@scope ::foo .b1}
$cmd configure -background red
set opts {-bg blue -fg white}
eval $cmd configure $opts
Note that scoped commands by-pass the usual protection mechanisms; the command:
@scope ::foo {report {Hello World!}}
can be used to access the "foo::report" proc from any namespace context, even though it is private.
KEYWORDS
scope, callback, namespace, public, protected, private
itcl 3.0 code(n)