10 More Discussions You Might Find Interesting
1. IP Networking
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
2. Programming
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
3. UNIX for Advanced & Expert Users
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
4. Solaris
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
5. OS X (Apple)
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
6. UNIX for Advanced & Expert Users
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
7. Linux
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
8. IP Networking
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
9. UNIX for Advanced & Expert Users
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
10. IP Networking
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
TIMED(8) BSD System Manager's Manual TIMED(8)
NAME
timed -- time server daemon
SYNOPSIS
timed [-dtM] [-i network | -n network] [-F host ...]
DESCRIPTION
The timed utility is a time server daemon which is normally invoked at boot time from the rc.conf(5) file. It synchronizes the host's time
with the time of other machines, which are also running timed, in a local area network. These time servers will slow down the clocks of some
machines and speed up the clocks of others to bring them to the average network time. The average network time is computed from measurements
of clock differences using the ICMP timestamp request message.
The following options are available:
-d Enable debugging mode; do not detach from the terminal.
-i network
Add network to the list of networks to ignore. All other networks to which the machine is directly connected are used by timed.
This option may be specified multiple times to add more than one network to the list.
-F host ...
- Create a list of trusted hosts.
- Can take one or more parameters.
- timed will only accept trusted hosts as masters. If it finds an untrusted host claiming to be master, timed will suppress incom-
ing messages from that host and call for a new election.
- Use real host names (resolvable by RDNS) not aliases (eg in named(8) parlance: use A names, not C names).
- Use full names eg time1.domain.com not time1.
- -F automatically includes the functionality of -M (so -M does not need to asserted).
- If -F is not specified, all hosts on connected networks are treated as trustworthy.
-M Allow this host to become a timed master if necessary.
-n network
Add network to the list of allowed networks. All other networks to which the machine is directly connected are ignored by timed.
This option may be specified multiple times to add more than one network to the list.
-t Enable tracing of received messages and log to the file /var/log/timed.log. Tracing can be turned on or off while timed is running
with the timedc(8) utility.
The -n and -i flags are mutually exclusive and require as arguments real networks to which the host is connected (see networks(5)). If nei-
ther flag is specified, timed will listen on all connected networks.
A timed running without the -M nor -F flags will always remain a slave. If the -F flag is not used, timed will treat all machines as trust-
worthy.
The timed utility is based on a master-slave scheme. When timed is started on a machine, it asks the master for the network time and sets
the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and calls adjtime(2) to per-
form the needed corrections on the host's clock.
It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control utility. If the machine running the
master becomes unreachable, the slaves will elect a new master from among those slaves which are running with at least one of the -M and -F
flags.
At startup timed normally checks for a master time server on each network to which it is connected, except as modified by the -n and -i
options described above. It will request synchronization service from the first master server located. If permitted by the -M or -F flags,
it will provide synchronization service on any attached networks on which no trusted master server was detected. Such a server propagates
the time computed by the top-level master. The timed utility will periodically check for the presence of a master on those networks for
which it is operating as a slave. If it finds that there are no trusted masters on a network, it will begin the election process on that
network.
One way to synchronize a group of machines is to use ntpd(8) to synchronize the clock of one machine to a distant standard or a radio
receiver and -F hostname to tell its timed to trust only itself.
Messages printed by the kernel on the system console occur with interrupts disabled. This means that the clock stops while they are print-
ing. A machine with many disk or network hardware problems and consequent messages cannot keep good time by itself. Each message typically
causes the clock to lose a dozen milliseconds. A time daemon can correct the result.
Messages in the system log about machines that failed to respond usually indicate machines that crashed or were turned off. Complaints about
machines that failed to respond to initial time settings are often associated with ``multi-homed'' machines that looked for time masters on
more than one network and eventually chose to become a slave on the other network.
WARNINGS
Temporal chaos will result if two or more time daemons attempt to adjust the same clock. If both timed and another time daemon are run on
the same machine, ensure that the -F flag is used, so that timed never attempts to adjust the local clock.
The protocol is based on UDP/IP broadcasts. All machines within the range of a broadcast that are using the TSP protocol must cooperate.
There cannot be more than a single administrative domain using the -F flag among all machines reached by a broadcast packet. Failure to fol-
low this rule is usually indicated by complaints concerning ``untrusted'' machines in the system log.
FILES
/var/log/timed.log tracing file for timed
/var/log/timed.masterlog log file for master timed
SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4), networks(5), ntpd(8), timedc(8)
R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD.
HISTORY
The timed utility appeared in 4.3BSD.
BSD
February 11, 2008 BSD
