Sponsored Content
Top Forums Shell Programming and Scripting How to monitor send/receive bytes Post 302476254 by bartus11 on Wednesday 1st of December 2010 08:25:41 AM
Old 12-01-2010
Take a look at "snoop" command.
 

9 More Discussions You Might Find Interesting

1. IP Networking

Tcp Ip Send Receive Server Program

Requirements: A server program should read a file and send the message to the client . if the file is not there, then switch to the receive part of the same program and receive any messages from the socket. If no messages to receive then switch to send part of the program to... (2 Replies)
Discussion started by: Rajeshsu
2 Replies

2. UNIX for Dummies Questions & Answers

I can send but cannot receive mail with unix?

Hi all, First post! I have just discovered that I can use unix to send mail to a mail address. I normally use entourage for my mail. This unix mail is very intriguing to me, but something is not working... I tried the search, but could not find the answer... This works: (in terminal)... (1 Reply)
Discussion started by: bjorn
1 Replies

3. UNIX for Dummies Questions & Answers

Can send but not receive email

Hi, One of the users in our company can send but not receive email. We are using SENDMAIL in conjunction with procmail. The funny thing is that all his sent email is in his /var/spool/mail but the email client does not pick anything up! He is using IMAP. Anyone see have any ideas? (2 Replies)
Discussion started by: mojoman
2 Replies

4. Programming

Send/Receive buffer size??

Dear friends, How do I find the TCP send and receive buffer size? (1 Reply)
Discussion started by: nagalenoj
1 Replies

5. Shell Programming and Scripting

Send Receive Mails

Hi All, I am writing one script to automate one long process. In this process we need to upload some input files and download some output files. So , I want to automate this upload and download by using mail functionality. I want to trigger this script when I am sending mail to server. I know... (0 Replies)
Discussion started by: NirajThakar
0 Replies

6. Shell Programming and Scripting

Script to monitor for new file with ext .err and size > 0 bytes and perform a action or command

Hi All, I need to create a script to monitor a dir for new files with ext .err and also it should b a non empty files. and perform a action or command . We have a new ETL application that runs on a linux server, every times a etl fails it creates a .err file or updates the existing .err... (4 Replies)
Discussion started by: MAKHAN
4 Replies

7. Solaris

zfs send receive performance issues

I 'm trying to clone a zfs file system pool/u01 to a new file system called newpool/u01 using following commands zfs list zfs snapshot pool/u01@new zfs send pool/u01@new | zfs -F receive newpool/u01 Its a 100G file system snapshot and copied to same server on different pool and... (9 Replies)
Discussion started by: fugitive
9 Replies

8. Shell Programming and Scripting

Send/receive file through serial using minicom

i have connected with my board through serial interface using minicom and i am running a bash script, which should test ethernet (ping test), USB read/write, RS232 .. I have managed to test ethernet and USB read/write. I test ethernet with ping. I test USB read/write, using dd and verifying... (10 Replies)
Discussion started by: linuxmember
10 Replies

9. IP Networking

Can not send files bigger than 1350 bytes

I am sending files over WAN from Ubuntu 8 to OSR 5.07 on regular basis without a problem using ftp and rsync. Today I can not send anything bigger than ~1350 bytes, tried ftp, rsync, scp, it becomes frozen and I have to kill the process. Smaller files are sent without issue. Telnet and ssh... (1 Reply)
Discussion started by: migurus
1 Replies
niffconfig(8)						      System Manager's Manual						     niffconfig(8)

NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF) SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...] OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options. Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame- ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout). Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout). DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter- faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command. Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified. EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0 SEE ALSO
Daemons: niffd(8) Information: EVM(5), nifftmt(7) niffconfig(8)
All times are GMT -4. The time now is 10:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy