10-23-2004
source quelch
I'm sorry in advance for not having all the information that may be needed to answer this post.
At my company we are trying to transfer a large amount of data from an NT server to a HP-UX server using ftp. The problem is that when transferring data we are getting extremely slow speeds of 240KB/sec and we are going to be transferring ~100GB!
We had the network group put a sniffer on to trace what is going on and they said on the network level everything is ok, but they said the destination server is sending "source quelch" messages back to the source server, which is causing the source server to slow down the transfer. Can anyone explain this in more detail and does this sound like a likely scenario or are the network guys telling me a story?
Thanks.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i'm installing qt from source, and while making i get an error having to do with a "pthread library." what libraries do i need to install for qt to compile, and where can i get them? (1 Reply)
Discussion started by: nydel
1 Replies
2. Solaris
Back some time ago, Sun had a pay/download Solaris source program. I had participated, but have since lost the source. Does anyone have such that they could make available.
Thanks much,
Keith (3 Replies)
Discussion started by: kduffin
3 Replies
3. Shell Programming and Scripting
What's the difference of using "." and "source", such as
". .bashrc" and "source .bashrc"? (1 Reply)
Discussion started by: learn
1 Replies
4. Shell Programming and Scripting
Hi I'm trying to write a script in which,if i log onto a particular server,the script should automatically find the server i'm on (which is the source server).We can find it frm the path /transfer/common/utilities/env_params.txt
please help me as to how start with this,shall i use the read cmmnd... (1 Reply)
Discussion started by: bkan77
1 Replies
5. UNIX Benchmarks
The link to download the source is broken. It's putting me back to the beginning forum page. (2 Replies)
Discussion started by: thywyn
2 Replies
6. Shell Programming and Scripting
I have a script in /etc/rc2.d that needs to run on boot up
the file looks like this
#!/sbin/sh
source /abc/scripts/test_env.sh
/abc/xyz/run
I need to source the test_env.sh script they are both bash how do i do that?
'source /abc/scripts/test_env.sh'
I am not too sure (3 Replies)
Discussion started by: deaconf19
3 Replies
7. UNIX for Advanced & Expert Users
Hi all.
I am trying to include the output of a command in a shell script (sh shell) but with no success.
Scenario is this: I have some XML and binary configuration files and I have an executable who writes a file with some shell variables I usually include in my shell script (executable... (7 Replies)
Discussion started by: ticiotix
7 Replies
8. Shell Programming and Scripting
Dear friends,
I am using SCO Openserver 5.0.7.
Where does the ps -ef command pick the information from? Is it stored in some file?
Also, the ps -ef command or the ps -eo args command displays truncated information. How to get the complete expanded output without truncation?
Thanks in... (8 Replies)
Discussion started by: sabu
8 Replies
9. Shell Programming and Scripting
Dear all,
For setting up my working environment, I need to source some files. What i usualy do is to do it manually,
cd /setup
source setup.sh
it take care of everything and I am able to run the commands like root.
As it was manual task every time, I defined this in .bashrc itself like... (12 Replies)
Discussion started by: emily
12 Replies
yppush(1M) yppush(1M)
NAME
yppush - force propagation of Network Information Service database
SYNOPSIS
domain] host] maxm] mint] mapname
Remarks
The Network Information Service (NIS) was formerly known as Yellow Pages (YP). Although the name has changed, the functionality of the
service remains the same.
DESCRIPTION
copies a Network Information Service (NIS) map (database), mapname, from the map's master NIS server to each slave NIS server. It is usu-
ally executed only on the master NIS server by shell script which is run either after changes are made to one or more of the master's NIS
databases or when the NIS databases are first created. See ypmake(1M) and ypinit(1M) for more information on these processes.
constructs a list of NIS server host names by reading the NIS map within the domain. Keys within the map are the host names of the
machines on which the NIS servers run. then sends a "transfer map" request to the NIS server at each host, along with the information
needed by the transfer agent (the program that actually moves the map) to call back
When the transfer attempt is complete, whether successful or not, and the transfer agent sends a status message, the results can be printed
to standard output. Messages are printed when a transfer is not possible, such as when the request message is undeliverable or when the
timeout period on responses expires.
Refer to ypfiles(4) and ypserv(1M) for an overview of Network Information Service.
Options
recognizes the following options:
Copy mapname to the NIS servers in domain rather than to the domain returned by (see domainname(1)).
Propagate the map(s) only to the specified host.
Attempt to run
maxm transfers in parallel to as many servers simultaneously. Without the option, attempts to transfer a map to each
server, one at a time. When a network has many servers, such serial transfers can result in long delays to complete all
transfers. A maxm value greater than 1 reduces total transfer time through better utilization of CPU time at the mas-
ter. maxm can be any value from 1 through the number of NIS servers in the domain.
Set the minimum timeout value to
mint seconds. When transferring to one slave at a time, waits up to 80 seconds for the transfer to complete, after
which it begins transferring to the next slave. When multiple parallel transfers are attempted by use of the option, it
may be necessary to set the transfer timeout limit to a value larger than the default 80 seconds to prevent timeouts
caused by network delays related to parallel transfers.
Verbose mode:
messages are printed when each server is called and when each response is received. If this option is omitted, only
error messages are printed.
WARNINGS
In the current implementation (Version 2 NIS protocol), the transfer agent is ypxfr(1M) which is started by the ypserv(1M) program at
yppush's request (see ypxfr(1M) and ypserv(1M)).
Starting with ONCplus version B.11.31.02, the NIS Version 1 protocol is no longer available.
AUTHOR
was developed by Sun Microsystems, Inc.
FILES
SEE ALSO
domainname(1), ypserv(1M), ypxfr(1M), ypfiles(4).
yppush(1M)