05-29-2008
Pipes not working
Hi,
thanks for b4. can anyone tell me why following not working:
noUsers=$(who | cut -d" " -f1 | wc -l)
What i'm trying to do is get a list of logged on users and pass it to 'wc -l' and store the output to a variable. Any ideas?
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hello!
How I can increase or decrease predefined pipe buffer size?
System FreeBSD 4.9 and RedHat Linux 9.0
Thanks! (1 Reply)
Discussion started by: Jus
1 Replies
2. Shell Programming and Scripting
Hi,
Can the cd command be invoked using pipes???
My actual question is slightly different. I am trying to run an executable from different folders and the path of these folders are obtained dynamically from the front end. Is there a way in which i can actually run the executable... (2 Replies)
Discussion started by: Sinbad
2 Replies
3. Programming
Extremely need to understand some aspects of pipes realization. The main question is in which memory are pipes placed? (13 Replies)
Discussion started by: pranki
13 Replies
4. Shell Programming and Scripting
can we use pipes to redirect the output of any command to grep .....
like i wanted to write this script about checking the online status of a certain user so ...can i send the output of who to grep directly using pipes...
one way was this :
who > temp
grep $uname temp
i was wondering if... (4 Replies)
Discussion started by: evergreen_cool
4 Replies
5. UNIX for Advanced & Expert Users
This is something I've given a lot of thought to and come up with no answer.
Say you have a data stream passing from a file, through process A, into process B. Process A only modifies a few bytes of the stream, then prints the rest of the stream unmodified. Is there any way to stream the file... (4 Replies)
Discussion started by: Corona688
4 Replies
6. UNIX for Dummies Questions & Answers
I have written the following program. The function of this prog is to read data from a file(source.c) and write into another file(dest.c) using pipes. I have just written a line in the source file.Im able to compile and run the program without errors. But the data is not written onto the other... (2 Replies)
Discussion started by: afser
2 Replies
7. Programming
Hello all, I am trying to learn more about programming Unix pipes in C.
I have created a pipe that does od -bc < myfile | head
Now, I am trying to create od -bc < myfile | head | wc
Here is my code, and I know I might be off, thats why I am here so I can get some clarification.
#include... (1 Reply)
Discussion started by: petrca
1 Replies
8. Shell Programming and Scripting
Hi,
I'm trying avoid having a large number of 'if' statements in my script by setting up a variable within 'ksh' which can be expanded depending on parameters passed to the script. The output from the 'cat' command should be able pipe its output into any additional commands on the command line... (4 Replies)
Discussion started by: stv_t
4 Replies
9. Programming
problem solved. (1 Reply)
Discussion started by: superfons
1 Replies
10. Programming
If a code forks 2 childs, what can the values be for the process id's of each of the child? I child pid is supposed to be 0, but what if you fork 2 of them? (5 Replies)
Discussion started by: omega666
5 Replies
LEARN ABOUT DEBIAN
cut-diff
CUT-DIFF(1) Cutter's manual CUT-DIFF(1)
NAME
cut-diff - show difference between 2 files with color
SYNOPSIS
cut-diff [option ...] file1 file2
DESCRIPTION
cut-diff is a diff command that uses diff feature in Cutter. It shows difference with color.
It's recommended that you use a normal diff(1) when you want to use with patch(1) or you don't need color.
OPTIONS
--version
cut-diff shows its own version and exits.
-c [yes|true|no|false|auto], --color=[yes|true|no|false|auto]
If 'yes' or 'true' is specified, cut-diff uses colorized output by escape sequence. If 'no' or 'false' is specified, cut-diff never
use colorized output. If 'auto' or the option is omitted, cut-diff uses colorized output if available.
The default is auto.
-u, --unified
cut-diff uses unified diff format.
--context-lines=LINES
Shows diff context around LINES.
All lines are shown by default. When unified diff format is used, 3 lines are shown by default.
--label=LABEL, -L=LABEL
Uses LABEL as a header label. The first--label option value is used as file1's label and the second --label option value is used
asfile2's label.
Labels are the same as file names by default.
EXIT STATUS
The exit status is 0 for success, non-0 otherwise.
TODO: 0 for non-difference, 1 for difference and non-0 for errors.
EXAMPLE
In the following example, cut-diff shows difference between file1 and file2:
% cut-diff file1 file2
In the following example, cut-diff shows difference between file1 and file2 with unified diff format:
% cut-diff -u file1 file2
SEE ALSO
diff(1)
Cutter February 2011 CUT-DIFF(1)