Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #62
Difficulty: Easy
DNS in Internet terms stands for the 'Domain Name System'.
True or False?
Linux & Unix Commands - Search Man Pages

ng_tee(4) [osx man page]

NG_TEE(4)						   BSD Kernel Interfaces Manual 						 NG_TEE(4)

NAME
ng_tee -- netgraph ``tee'' node type SYNOPSIS
#include <sys/types.h> #include <netgraph/ng_tee.h> DESCRIPTION
The tee node type has a purpose similar to the tee(1) command. Tee nodes are useful for debugging or ``snooping'' on a connection between two netgraph nodes. Tee nodes have four hooks, right, left, right2left, and left2right. All data received on right is sent unmodified to both hooks left and right2left. Similarly, all data received on left is sent unmodified to both right and left2right. Packets may also be received on right2left and left2right; if so, they are forwarded unchanged out hooks right and left, respectively. HOOKS
This node type supports the following hooks: right The connection to the node on the right. left The connection to the node on the left. right2left Tap for right to left traffic. left2right Tap for left to right traffic. CONTROL MESSAGES
This node type supports the generic control messages, plus the following. NGM_TEE_GET_STATS Get statistics, returned as a struct ng_tee_stats. NGM_TEE_CLR_STATS Clear statistics. SHUTDOWN
This node shuts down upon receipt of an NGM_SHUTDOWN control message, or when all hooks have been disconnected. If both right and left hooks are present, node removes itself from the chain gently, connecting right and left together. SEE ALSO
tee(1), netgraph(4), ngctl(8) HISTORY
The ng_tee node type was implemented in FreeBSD 4.0. AUTHORS
Julian Elischer <julian@FreeBSD.org> BSD
May 28, 2004 BSD

Check Out this Related Man Page

NG_TEE(4)                                                  BSD Kernel Interfaces Manual                                                  NG_TEE(4)

NAME
ng_tee -- netgraph ``tee'' node type SYNOPSIS
#include <sys/types.h> #include <netgraph/ng_tee.h> DESCRIPTION
The tee node type has a purpose similar to the tee(1) command. Tee nodes are useful for debugging or ``snooping'' on a connection between two netgraph nodes. Tee nodes have four hooks, right, left, right2left, and left2right. All data received on right is sent unmodified to both hooks left and right2left. Similarly, all data received on left is sent unmodified to both right and left2right. Packets may also be received on right2left and left2right; if so, they are forwarded unchanged out hooks right and left, respectively. HOOKS
This node type supports the following hooks: right The connection to the node on the right. left The connection to the node on the left. right2left Tap for right to left traffic. left2right Tap for left to right traffic. CONTROL MESSAGES
This node type supports the generic control messages, plus the following. NGM_TEE_GET_STATS Get statistics, returned as a struct ng_tee_stats. NGM_TEE_CLR_STATS Clear statistics. SHUTDOWN
This node shuts down upon receipt of an NGM_SHUTDOWN control message, or when all hooks have been disconnected. If both right and left hooks are present, node removes itself from the chain gently, connecting right and left together. SEE ALSO
tee(1), netgraph(4), ngctl(8) HISTORY
The ng_tee node type was implemented in FreeBSD 4.0. AUTHORS
Julian Elischer <julian@FreeBSD.org> BSD May 28, 2004 BSD

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

log script input and output using tee ?

hi, new to to forum... i've been trying to create a script in tcsh but i'm having a problem with one thing... the script has to keep log of it's input and output so i'm using tee -a log | script | tee -a log this keeps the logs as asked, but it gives me an extra empty prompt (not in the... (0 Replies)
Discussion started by: moseschrist
0 Replies

2. Shell Programming and Scripting

removing tee

Hi, I have a script where i want to log in details to the standard output as well as log file so that its easy for tracing purposes. I have used the "tee"command. The problem with this is my scripts lines are getting longer as for each line i have #!/bin/ksh echo "hello world" |... (4 Replies)
Discussion started by: pinnacle
4 Replies

3. Shell Programming and Scripting

STDERR to file & terminal using tee

Hi All, Solarix/Bash v3x Im trying to output any standard errors created by the script to a file using the below command: . runDTE.sh 2> "$DTE_ERROR_FILE" however the errors do get written to the dir/file stored in $DTE_ERROR_FILE but the error does not appear on the terminal screen in... (4 Replies)
Discussion started by: satnamx
4 Replies

4. Shell Programming and Scripting

Using tee

I have been using the command tee to store the output to a file and also write on the terminal. However I would need to put the program in the background although I would still need to see the file being updated like it was doing when using tee. Any suggestions on how to look at the log file... (3 Replies)
Discussion started by: kristinu
3 Replies

5. UNIX for Dummies Questions & Answers

Problem using tee to capture activity - nothing happens

Hi, I'm sure this is real simple but in the looking I've done I haven't seen it addressed (or didn't realize it). I've started up a PuTTY connection to our UNIX box and started screen and script - no problems. Then I typed "tee teeKH18.txt" expecting it to start tee and dump all activity into... (2 Replies)
Discussion started by: Mike Welch
2 Replies

6. Shell Programming and Scripting

Using tee causing need for extra newlines.

I am working on capturing lines of output from a korn script that is used to import optical disks into a jukebox. The script is running on Solaris 8. Insertdiscs calls the binary named vimport which starts up and prompts for a disk to be inserted. I am able to capture output with this line below... (3 Replies)
Discussion started by: buggin
3 Replies

7. Shell Programming and Scripting

Automatically send stdout and stderror to a file as well as to the screen, but without using tee

Hi, I've been using the following commands in my automated scripts, to ensure that all text output is sent to a log file instead of to the screen: exec 1>>$SCRIPT_LOG_FILE exec 2>>$SCRIPT_LOG_FILE However, I've now discovered that the system used for automating the script executions... (4 Replies)
Discussion started by: confusedAdmin
4 Replies

8. UNIX for Beginners Questions & Answers

Using tee command with ablity to provide input for prompts

OS version: RHEL 7.4 Shell : bash I would like to capture command outputs using tee like # yum upgrade | tee yumupgradeLog But, if I use tee command, I cannot respond to prompts like Is this ok : during command execution as shown below. Is there a way I could use tee and still be able to... (4 Replies)
Discussion started by: kraljic
4 Replies

Featured Tech Videos