Sponsored Content
Operating Systems Linux Red Hat application to be run on machines connected in same network Post 302311129 by pradeepreddy on Tuesday 28th of April 2009 02:13:40 AM
Old 04-28-2009
application to be run on machines connected in same network

I have a set up of 5 machines which are connected in same network.

Now i want to run a small application so that those machines are not ideal.
 

10 More Discussions You Might Find Interesting

1. IP Networking

How can i simulate network problems between unix machines ?

Hello all i need to simulate method invocations between 2 machine ( using corba ) now i like to test the method invoke timeout from machine1 to machine2 for that i need to simulate network being busy , can it be done some how ? (2 Replies)
Discussion started by: umen
2 Replies

2. UNIX for Advanced & Expert Users

ping all the machines in the network

Is there any option for the utility "ping" , which can ping all the machines in the network? (5 Replies)
Discussion started by: praveen_b744
5 Replies

3. IP Networking

check whether connected to network

hi... can anyone pls suggest a few methods to check whether a computer is connected to any network, using the terminal, not GUI. thanks eskay (1 Reply)
Discussion started by: eskay_karthik
1 Replies

4. Linux

How to mount a filesystem of one pc in another pc that are connected in a network?

Hi, I have a software in one of the pcs connected in the network and I need to mount that file system in my PC. Both the pcs have Linux installed. Please let me know how can we achieve this. Any pointers would be of great help. Thanks & Regards, Venkatesh. (3 Replies)
Discussion started by: venkatesh_sasi
3 Replies

5. UNIX for Advanced & Expert Users

check external hardware connected to linux/solaris machines

hello, I'm planning to do inventory of all our servers but this time it's more on physical. Meaning I would like to check all hardware connected to it (external only like storage, power support) including the count Would like to get perhaps its serial nr..(linux and solaris different servers... (2 Replies)
Discussion started by: lhareigh890
2 Replies

6. OS X (Apple)

Where do I find my mac that is connected via Firewire in Terminal application?

I have my iMac and MB pro connected by firewire. I can see the connection in the finderwindow, but can't locate the machines in terminal. Can someone help me? I do most of my work in Terminal and would like to move/copy files from one machine to another like that -- I could have sworn I was able... (4 Replies)
Discussion started by: Straitsfan
4 Replies

7. Solaris

Solaris 8: Multiple primary interfaces connected to the same network

Hello, I have a machine with Solaris 8, and it has multiple interfaces that are connected to the same network which means they all have metric 0 (1 hop) to the default gateway. assume: * e1000g0: 10.1.1.70 * e1000g2: 10.1.1.72 * e1000g4: 10.1.1.74 * e1000g5: 10.1.1.76 * gateway:... (11 Replies)
Discussion started by: aeg
11 Replies

8. UNIX for Advanced & Expert Users

Connected to the internet with no network process

This is what I did. $ ps -ef | grep -i networkroot 6657 1 0 12:55 ? 00:00:01 /usr/sbin/NetworkManager bob 7251 7212 0 13:24 pts/3 00:00:00 grep --color=auto -i $ sudo kill -9 6657 password for bob: $ ping -c 5 google.com PING google.com (74.125.229.160)... (1 Reply)
Discussion started by: cokedude
1 Replies

9. Programming

Application behaving in 3 different ways on 3 different machines

Hello. During the holidays I've been developing an application on my desktop computer at home. I setup a repository on github, so when I got back to work I cloned the repo to my laptop. It wouldn't work. The app is comprised of a client and a server, strangely enough the server would segfault... (10 Replies)
Discussion started by: erupter
10 Replies

10. IP Networking

Discover Windows machines in other network

I have my Windows computer in network 192.168.1.0/24 plugged into one interface of my router. I have another port on the router as network 192.168.168.0/24 where my nas is plugged in. Now Windows doesn't discover my NAS automatically, of course. Anyone know what would be the most elegant way to... (2 Replies)
Discussion started by: awayand
2 Replies
timed(8)						      System Manager's Manual							  timed(8)

NAME
timed - The network time daemon SYNOPSIS
timed [-tME] [-n | -i network] FLAGS
Specifies the names of the networks (as defined in the /etc/networks file) to be excluded from clock synchronization. Each network name that is an argument to the -i flag is added to the list of networks that the timed daemon will ignore. If the -i flag is used, timed accesses all networks to which the host is connected except for the specified networks. If neither the -i flag nor the -n flag is used, timed tries to access all the network devices connected to the local host. Do not use the -i and -n flags together. Specifies that a machine can become the time server if the master time server becomes inoperative. See the Restrictions section for more information. Overrides the input of slaves. Use the -E flag in conjunction with the -M flag. It specifies that a master timed system will not average the times of the slaves to calculate the network time. Instead, it distributes the time of its local host as the network time. This flag allows a master timed system to distribute time to a network while the network time is controlled by an outside agent (such as the Network Time Protocol (NTP)). Specifies the names of the networks (as defined in the /etc/networks file) to be included in clock synchronization. When timed is started, it gathers information about all the network devices connected to the local host. The network argument to the -n flag is the name of the network that timed should access. If the -n flag is used, only the specified networks are accessed. If neither the -n flag nor the -i flag is used, timed tries to access all the network devices connected to the local host. Do not use the -n and -i flags together. Enables tracing of messages received in /usr/adm/timed.log. DESCRIPTION
The timed daemon is not invoked at boot time by default. You can use /usr/sbin/timedsetup to configure the timed daemon. The timed daemon synchronizes the host's clock with those of other machines on the local area network that are also running the timed dae- mon. The timed daemon slows the clocks of some machines and speeds up the clocks on other machines to create an average network time. The average network time is computed from measurements of clock differences using the Internet Control Message Protocol ICMP timestamp request message. The service provided by timed is based on a master/slave (client/server) scheme. When timed is started on a machine, it asks the master timed daemon for the network time and sets the host's clock to that time. After that, the host accepts synchronization messages periodi- cally sent by the master and calls the adjtime system call to perform the needed corrections on the host's clock. The timed daemon also communicates with the date command to set the date globally, and with timedc, the timed control program. If the machine running the master ceases to function, a machine that is running the timed daemon with the -M flag becomes the new master timed daemon. Note The timed daemon is provided for compatibility. Tru64 UNIX also provides support for the Network Time Protocol through the xntpd daemon. You should use NTP for time synchronization. If you need to run both NTP and the timed daemon, you must run the timed daemon with the -E flag. If you plan to run both the timed daemon and NTP, you should also configure NTP first. RESTRICTIONS
In configurations with two or more hosts each connected to the same two or more subnetworks, only one of the host can run the timed with the -M option. FILES
Specifies the command path Contains messages traced for the timed command Contains information about the known networks RELATED INFORMATION
Commands: date(1), timedc(8), timedsetup(8) Daemons: xntpd(8) Functions: adjtime(2), gettimeofday(2) delim off timed(8)
All times are GMT -4. The time now is 07:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy