Following command was set up in startup script on Solaris 8 servers - improved network transfers of files from one server to the another [server B has duplicate entry in it's startup script except the IP is changed to server A] (doubled transfer speed).
Now they are getting a new server with Solaris 10 on it - setting the same command in a startup script does NOTHING for the speed of the transfer.
both networks are 100 MB - new server on same subnet as old one. New server will get old server's IP (so nothing on the server B side has to change)
Anyone know what might be the 'new' way of doing this for Solaris 10?
Last edited by Scott; 03-05-2010 at 01:12 AM..
Reason: Code tags
Hello,
I am totally new to Unix. My current contract requires me to build an intranet site (nothing fancy, no forms, no cgi scripts, no search engine) for a unix platform.
I develop on an NT environment using dreamweaver.
I am considering buying Red Hat Linux, install that on the NT... (1 Reply)
I am trying to set an interface to 100/Full, but the command I use are getting rejected. I think it is the last argument, but I don't know how to find the correct values.
I am trying to use the following script, but change hme to le .
echo "Setting hme interface 1: 100mb/full-duplex..."
... (2 Replies)
Hi Guys,
I need help with ndd.
I was going through network FAQ but i have more questions then answers regarding ndd.
#ndd -set /dev/hme instance 0
#ndd -set /dev/hme adv_100fdx_cap 1
#ndd -set /dev/hme adv_100hdx_cap 0
#ndd -set /dev/hme adv_10fdx_cap 0
#ndd -set /dev/hme adv_10hdx_cap 0... (2 Replies)
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Hi,
I would like to know whether there is any config file that i can refer to for the result of 'ndd -get /dev/tcp tcp_time_wait_interval'?
When i man 'ndd', there is one statement which is -> Each driver chooses which parameters to make visible using ndd. Does it answering my question above... (3 Replies)
Solaris 10 server (SunOS 5.10 Generic_137137_09)
I have a services file configured in /etc in there windows clients connect to my server on port 6034-6037
when I do the following
netstat | grep TestServices
it pulls all the connections active for those ports
so right now I have 10 clients... (3 Replies)
While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out?
An early response will be appreciated.
Thank you
Regards
TCG (2 Replies)
on RHEL 5.3 i did
mount -o remount,rw /dev/hda8 ( this is /tmp directory )
now OS not coming up.
How to resolve ??
---------- Post updated at 04:57 PM ---------- Previous update was at 03:36 PM ----------
one of my friend told me that you have changed sticky bit permissions on /tmp... (6 Replies)
Hello forum,
I have a Solaris 9 Sun Fire v240 server and Sun Fire v440
Recently we made changes and installed a new switch which both of them are connected to it. Cisco Catalyst 3750.
Now the Sun Server v240 is having problems with the network. It was supposed to run at 1000mbs speed.
ndd... (10 Replies)
I have a command to check the status of hostname and port number,
echo > /dev/tcp/hostname/80
echo $?
0
success case
echo > /dev/tcp/hostname/809999
I got the output
-------------------
connection timed out
It took almost 4 minutes to time out,,, how can I set it to 10 seconds?
my... (2 Replies)
Discussion started by: sam@sam
2 Replies
LEARN ABOUT HPUX
yppush
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)