03-17-2014
There are two catches... One, it can only alter the rate of transmission, not reception. Two, it's only precise on average.
10 More Discussions You Might Find Interesting
1. IP Networking
I am running Mandrake 8.0 (KDE ver 2.1.1) on a machine with 2 NICs. This is a college project. I am attempting to configure this machine as a firewall, and to pass packets from one network to another. Eth0 is on my external network. Eth1 is on my internal network. I set the gateway in "netconf"... (1 Reply)
Discussion started by: Deuce
1 Replies
2. UNIX for Dummies Questions & Answers
there are commands to monitor the memory, paging, io... how about network traffic. i mean commands to see whether the network traffic (LAN) is congested? the closest i got is netstat
thanks (6 Replies)
Discussion started by: yls177
6 Replies
3. Cybersecurity
Hi,
Can someone give me the clue on how to capture network traffic at gateway.
Thanx (2 Replies)
Discussion started by: kayode
2 Replies
4. UNIX for Advanced & Expert Users
I want to monitor network traffic. For this purpose i use snoop command. But snoop command only show those packets which are broadcasted or those packets which recieved by host. But I want to examine whole network traffic. Please tell me how to use snoop for monitoring whole network traffic or if... (3 Replies)
Discussion started by: mansoorulhaq
3 Replies
5. Infrastructure Monitoring
Hi all,
Got a strange one here, well not so much strange, different :-)
I need to work out if a server is particulary chatty, whether its talking / communicating heavily to a particular server, as Im planning to physically move the server to a different server, over a link. Hence the... (6 Replies)
Discussion started by: sbk1972
6 Replies
6. HP-UX
I Colleagues,
Somebody can say me how to monitoring traffic in the network. also I am interested in monitoring memory. if somebody to know a guide with command advanced in unix welcome for me.
Thank you for adcanced. (0 Replies)
Discussion started by: systemoper
0 Replies
7. IP Networking
hi all
i want to extract few connection level features (not packet level )of the internet traffic through ethernet card interface
the features are as follows
Timestamp Timestamp of paket captured
Duration duration of connection
ip_proto IP... (0 Replies)
Discussion started by: vaibhavkorde
0 Replies
8. Shell Programming and Scripting
hi all
i want to extract few connection level features (not packet level )of the internet traffic through ethernet card interface
the features are as follows
Timestamp Timestamp of paket captured
Duration duration of connection
ip_proto IP... (2 Replies)
Discussion started by: vaibhavkorde
2 Replies
9. Infrastructure Monitoring
If I would like to know what connection , data , traffic in a network port ( eth0 ) , what can I do ?
ps. because I always found the network is very slow , so I would like what the network port is doing .
Thanks
Login ID ust3 is currently in read-only mode for multiple infractions. Creating... (0 Replies)
Discussion started by: ust03
0 Replies
10. IP Networking
My son does homework on a school laptop. I was thinking about setting up a gateway on my home network, so that I can monitor web traffic and know if he is doing his homework without standing over his shoulder. Ideally I would like to use the Raspberry Pi Model b that I already have. However, I... (15 Replies)
Discussion started by: gandolf989
15 Replies
LEARN ABOUT DEBIAN
ltpclock
LTPCLOCK(1) LTP executables LTPCLOCK(1)
NAME
ltpclock - LTP daemon task for managing scheduled events
SYNOPSIS
ltpclock
DESCRIPTION
ltpclock is a background "daemon" task that periodically performs scheduled LTP activities. It is spawned automatically by ltpadmin in
response to the 's' command that starts operation of the LTP protocol, and it is terminated by ltpadmin in response to an 'x' (STOP)
command.
Once per second, ltpclock takes the following action:
First it manages the current state of all links ("spans"). In particular, it checks the age of the currently buffered session block
for each span and, if that age exceeds the span's configured aggregation time limit, gives the "buffer full" semaphore for that span to
initiate block segmentation and transmission by ltpmeter.
In so doing, it also infers link state changes ("link cues") from data rate changes as noted in the RFX database by rfxclock:
If the rate of transmission to a neighbor was zero but is now non-zero, then transmission to that neighbor is unblocked. The
applicable "buffer empty" semaphore is given if no outbound block is being constructed (enabling start of a new transmission
session) and the "segments ready" semaphore is given if the outbound segment queue is non-empty (enabling transmission of segments
by the link service output task).
If the rate of transmission to a neighbor was non-zero but is now zero, then transmission to that neighbor is blocked -- i.e., the
semaphores triggering transmission will no longer be given.
If the imputed rate of transmission from a neighbor was non-zero but is now zero, then all timers affecting segment retransmission
to that neighbor are suspended. This has the effect of extending the interval of each affected timer by the length of time that
the timers remain suspended.
If the imputed rate of transmission from a neighbor was zero but is now non-zero, then all timers affecting segment retransmission
to that neighbor are resumed.
Then ltpclock retransmits all unacknowledged checkpoint segments, report segments, and cancellation segments whose computed timeout
intervals have expired.
EXIT STATUS
0 ltpclock terminated, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem
identified in the log file and use ltpadmin to restart ltpclock.
1 ltpclock was unable to attach to LTP protocol operations, probably because ltpadmin has not yet been run.
FILES
No configuration files are needed.
ENVIRONMENT
No environment variables apply.
DIAGNOSTICS
The following diagnostics may be issued to the ion.log log file:
ltpclock can't initialize LTP.
ltpadmin has not yet initialized LTP protocol operations.
Can't dispatch events.
An unrecoverable database error was encountered. ltpclock terminates.
Can't manage links.
An unrecoverable database error was encountered. ltpclock terminates.
BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>
SEE ALSO
ltpadmin(1), ltpmeter(1), rfxclock(1)
perl v5.14.2 2012-05-25 LTPCLOCK(1)