Sponsored Content
Operating Systems Solaris Network writes contantly spiking in throughput Post 302377976 by DukeNuke2 on Sunday 6th of December 2009 05:56:57 AM
Old 12-06-2009
have you tuned the mtu packet size? what kind of switch (managed/unmanaged) do you use? can you connect the boxes with a cross cabel and check if the problem persists? is autoneg used?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

how can i test my tape throughput in Mb/sec?

Is there a tool or cmd line program i can use to test my tape throughput in Mb/sec? thank you (2 Replies)
Discussion started by: progressdll
2 Replies

2. Shell Programming and Scripting

Contantly check for file at the remote server and ftp when avaliable

Hello, I used the search engine but could not find the solution I am looking for. Probably its simple but I do not know the solution. My requirement is I ftp files every day in the morning from the remote server to the local machine. Now if the files are not there at the time I schedule the ftp... (2 Replies)
Discussion started by: kiran_418
2 Replies

3. UNIX for Advanced & Expert Users

tool to monitor throughput

Was wonder if there was a tool or program I could run to measure throughput on our CentoS 4.x server. Our current dedicated host provider is charging us by how much throughput we are using and I just want to see if their numbers add up to whatever I get using a throughput tool of some kind. ... (6 Replies)
Discussion started by: mcraul
6 Replies

4. IP Networking

Gigabit Link throughput

As a rule of thumb in doing calculations, what figure would you use in Mbytes/sec? I know the answer varies grealty on the topolgy of the network but I wonde what newteok engineers use a rough rule of thumb? Many thanks. (1 Reply)
Discussion started by: debd
1 Replies

5. IP Networking

How to improve throughput?

I have a 10Gbps network link connecting two machines A and B. I want to transfer 20GB data from A to B using TCP. With default setting, I can use 50% bandwidth. How to improve the throughput? Is there any way to make throughput as close to 10Gbps as possible? thanks~ :) (3 Replies)
Discussion started by: andrewust
3 Replies

6. HP-UX

Performance - CPU spiking

We have a DB server which is constantly utilised above 95% above. This is becoming nuisance when the monitoring team frequently calls to check on it. Frankly I do not know what to tweak or even interpret the outputs. I noticed constant 30 to 60% in wio column of the cpu utilisation. There... (1 Reply)
Discussion started by: sundar63
1 Replies

7. Solaris

Throughput problems with solaris aggregation

Hello gurus, I have the following configuration in the server side: # dladm show-aggr key: 33 (0x0021) policy: L4 address: 0:14:4f:6c:11:8 (auto) device address speed duplex link state nxge0 0:14:4f:6c:11:8 1000 Mbps ... (3 Replies)
Discussion started by: FERCA
3 Replies

8. IP Networking

Issue with ns2 - no throughput data

Hello, First time poster here hoping to get some help with ns2. I've recently started using ns2(first time user) but I'm having difficulty getting the results I'm after. I am trying to set up a network with wireless nodes(5-15 nodes) and then use xgraph to display a timing diagram,... (0 Replies)
Discussion started by: UnicksMan
0 Replies

9. IP Networking

OID for Bandwith and Throughput Measurement

Hey Guys, Does anybody know, which OID's of Net-SNMP is used to collect throughput and bandwith usage of machine?? I got these OID's ..iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry.ifOutOctets ..1.3.6.1.2.1.2.2.1.16 ... (1 Reply)
Discussion started by: franzramadhan
1 Replies
PROXYMNGR(1)						      General Commands Manual						      PROXYMNGR(1)

NAME
proxymngr - proxy manager service SYNOPSIS
proxymngr [-config filename] [-timeout seconds] [-retries #] [-verbose] DESCRIPTION
The proxy manager (proxymngr) is responsible for resolving requests from xfindproxy (and other similar clients), starting new proxies when appropriate, and keeping track of all of the available proxy services. The proxy manager strives to reuse existing proxies whenever possi- ble. There are two types of proxies that the proxy manager deals with, managed and unmanaged proxies. A managed proxy is a proxy that is started ``on demand'' by the proxy manager. An unmanaged proxy, on the other hand, is started either at system boot time, or manually by a system administrator. The proxy manager is made aware of its existence, but no attempt is made by the proxy manager to start unmanaged proxies. The command line options that can be specified to proxymngr are: -config Used to override the default proxymngr config file. See below for more details about the config file. -timeout Sets the number of seconds between attempts made by the proxy manager to find an unmanaged proxy. The default is 10. -retries Sets the maximum number of retries made by the proxy manager to find an an unmanaged proxy. The default is 3. -verbose Causes various debugging and tracing records to be displayed as requests are received and proxies are started. Proxy Manager Config File The proxy manager maintains a local configuration file describing the proxy services available. This configuration file is installed in /usr/X11R6/lib/X11/proxymngr/pmconfig during the installation of proxymngr. The location of the configuration file can be overwritten using the -config command line option. Aside from lines starting with an exclamation point for comments, each line of the configuration file describes either an unmanaged or man- aged proxy service. For unmanaged proxies, the format is: <service-name> unmanaged <proxy-address> service-name is the name of the unmanaged proxy service, and must not contain any spaces, for example ``XFWP''. service-name is case insensitive. proxy-address is the network address of the unmanaged proxy. The format of the address is specific to the service-name. For example, for the ``XFWP'' service, the proxy-address might be ``firewall.x.org:100''. If there is more than one entry in the config file with the same unmanaged service-name, the proxy manager will try to use the proxies in the order presented in the config file. For managed proxies, the format is: <service-name> managed <command-to-start-proxy> service-name is the name of the managed proxy service, and must not contain any spaces, for example ``LBX''. service-name is case insensi- tive. command-to-start-proxy is the command executed by the proxy manager to start a new instance of the proxy. If command-to-start-proxy con- tains spaces, the complete command should be surrounded by single quotes. If desired, command-to-start-proxy can be used to start a proxy on a remote machine. The specifics of the remote execution method used to do this is not specified here. EXAMPLE
Here is a sample configuration file: ! proxy manager config file ! ! Each line has the format: ! <serviceName> managed <startCommand> ! or ! <serviceName> unmanaged <proxyAddress> ! lbx managed /usr/X11R6/bin/lbxproxy ! ! substitute site-specific info xfwp unmanaged firewall:4444 PROXY MANAGER DETAILS
When the proxy manager gets a request from xfindproxy (or another similar client), its course of action will depend on the service-name in question. For a managed proxy service, the proxy manager will find out if any of the already running proxies for this service can handle a new request. If not, the proxy manager will attempt to start up a new instance of the proxy (using the command-to-start-proxy found in the config file). If that fails, an error will be returned to the caller. For an unmanaged proxy service, the proxy manager will look in the config file to find all unmanaged proxies for this service. If there is more than one entry in the config file with the same unmanaged service-name, the proxy manager will try to use the proxies in the order presented in the config file. If none of the unmanaged proxies can satisfy the request, the proxy manager will timeout for a configurable amount of time (specified by -timeout or default of 10) and reattempt to find an unmanaged proxy willing to satisfy the request. The num- ber of retries can be specified by the -retries argument, or a default of 3 will be used. If the retries fail, the proxy manager has no choice but to return an error to the caller (since the proxy manager can not start unmanaged proxy services). BUGS
proxy manager listen port should be configurable. -timeout and -retries is not implemented in proxymngr. proxymngr does not utilize the ``options'' and ``host'' fields in the proxy management protocol GetProxyAddr request. SEE ALSO
xfindproxy (1), xfwp (1), Proxy Management Protocol spec V1.0 AUTHOR
Ralph Mor, X Consortium XFree86 Version 4.7.0 PROXYMNGR(1)
All times are GMT -4. The time now is 01:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy