Sponsored Content
Full Discussion: Network related issues
Homework and Emergencies Emergency UNIX and Linux Support Network related issues Post 303002940 by jim mcnamara on Tuesday 5th of September 2017 11:41:21 AM
Old 09-05-2017
What OS? Your other post mentions AIX. Getting data from the past is really difficult unless you had already set up monitoring or auditing.

If you have detailed logs from applications, sometimes you can infer that application A has been taking longer and longer times to complete.

Many kinds of problems are sporadic or are hard to reproduce. These can only be found by creating monitors before the fact.

Please give us more system details: specific OS, main application(s) for the system.
Example: AIX 7.3, sybase server on SAN.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Network printer issues

Hello, I have been having a problem with printing to a network printer on my LAN, I am able to ping all ports from the server and the printer. Print request just stay in the print que the only way to print is from the parallel line to the server. Any ideas on what can be going wrong?? Lp sched is... (1 Reply)
Discussion started by: ostac
1 Replies

2. Solaris

Solaris 10 network, process, database related comands

Hi everbody, Can anyone let me know the resources for list of network, process, database related commands of solaris10 possibly with little bit of explanation. Thanks in advance, Chandra Sekhar. (1 Reply)
Discussion started by: chandoo.java
1 Replies

3. Programming

Fork syscall and related issues

Hi all, i just started started learning system programming and want to pursue a career in the sys prog area. below is the program that use a fork() call. i read in one of the tutorials that parent process and child process uses different address spaces and runs concurrently. that meas each... (2 Replies)
Discussion started by: MrUser
2 Replies

4. UNIX for Dummies Questions & Answers

Check for network issues

Hi all, How do i check for network issues on a server (solaris & linux) - interms of connectivity, collision, congestion, whatever that's impacting the connection to/from the server? Please advise. Thanks. :confused: (4 Replies)
Discussion started by: greencored
4 Replies

5. AIX

Network related errors

Hi How to check if my AIX server has any network related errors ? (2 Replies)
Discussion started by: samsungsamsung
2 Replies

6. Solaris

Swap space related issues, how to recognise the newly attached disk

hi!:) i got a problem....:wall::wall: i got several disks in my diskarray. I attached new disk to allocate it to the swap space. The problem is : how to recognise the newly attached disk? I've one more requirement -:wall:- i want to run dns service on another port number.how can i do... (2 Replies)
Discussion started by: vamshigvk475
2 Replies

7. HP-UX

Network Connectivity Issues

Newbie with UNIX here. Currently troubleshooting a UNIX terminal we have. I determined it to be bad and swapped it out with a known good terminal. I went in and changed the IP address and host name to reflect the old terminal. Although now there is no connectivity. I swapped out the NIC... (1 Reply)
Discussion started by: kevinlord190
1 Replies

8. Shell Programming and Scripting

Network related script

First of all,I would like to introduce about me, This is my own try and this is not my homework,and I study myself reading shell script pdf guide from net and learn shell scripts bit by bit.I am self study learner.I try to work out shell scripts.please help to resolve this type of problem.when I... (1 Reply)
Discussion started by: kannansoft1985
1 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)
All times are GMT -4. The time now is 05:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy