Sponsored Content
Special Forums IP Networking problem using rsh for ordinary users! Post 8737 by nikk on Wednesday 17th of October 2001 09:21:43 AM
Old 10-17-2001
This is 555 for mt command.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem with rsh

Hi all I have checked the archives and cannot find a solution. I get a permission denied error, however all the suggestions donot help. here is the scenario root@OPSBOX#/>rsh OPSBOX ls -l rshd: 0826-813 Permission is denied. root@OPSBOX#/>pg .rhosts OPSBOX root OPSBOX ... (1 Reply)
Discussion started by: jhansrod
1 Replies

2. Shell Programming and Scripting

rsh problem

Hi, I am using rsh command in scripting. But I wan to run the script as a bg process. When I run the script, it says stopped. My doubt is ....if I use the rsh in scripting ......bg is possible or not ??? EX: test-rsh rsh 172.16.73.38 df -k >DF.log Result when I run this script ... (5 Replies)
Discussion started by: vastare
5 Replies

3. UNIX for Dummies Questions & Answers

RSH password problem

Hello, I am currently trying to execute a command in a Windows machine from a UNIX server. In order to do this, I am using the RSH command in UNIX but whenever i do this I am getting this error "RSHD: <username>: could not retrieve password: Please login and run rsetup." I log in via the... (0 Replies)
Discussion started by: punyenye
0 Replies

4. Shell Programming and Scripting

rsh problem

hey, I'v a problem when I use rsh. When it logs in, it goes my home directory. I want it to go directly to my working directory. An idea I had was to redirect pwd to a file (pwd > somefile) and then once I'v rsh'd, cd to that path. I don't know how to read from the file to use as a parameter for... (2 Replies)
Discussion started by: Bacchus
2 Replies

5. Shell Programming and Scripting

rsh problem

I tried to execute by rsh a script, but I did not succeed. You can execute only commnads (not scripts) by rsh or there are some other restrictions?!? root@a1 #pwd / root@a1 #rsh a2 monitor ksh: monitor: not found On the other hand: root@a1 #rsh a2 root@a2 #pwd / root@a2 #ls monitor... (9 Replies)
Discussion started by: heartwork
9 Replies

6. Shell Programming and Scripting

rsh problem

Dear, I am trying to execute a script in the X machine by remote logging from machine Y. Note that in the X machine in host file the ip and the hostname of the Y is defined and in the .rhosts the hostname and the username of the Y is defined. By using the following: rsh X -l username -n "sh... (0 Replies)
Discussion started by: tontal
0 Replies

7. Shell Programming and Scripting

rsh connection problem

I am trying to connect to a remote server using rsh. first i have given the following command. $ rsh 242.13.45.54 -l now i got the following message "connect to address 242.13.45.54: Connection refused Trying krb4 rlogin... connect to address 242.13.45.54: Connection refused trying... (1 Reply)
Discussion started by: ravi raj kumar
1 Replies

8. UNIX for Dummies Questions & Answers

Problem using RSH

Hi, I have an old solaris 2.6 box and I need to copy all the data from the hard drive onto another machine. It does not have ssh installed so I am forced to use rsh. My plan was to execute the rcp command from the solaris box to a Centos 5 machine. I have installed rsh client and server on my... (1 Reply)
Discussion started by: mojoman
1 Replies

9. UNIX for Dummies Questions & Answers

RSH/rlogin problem

Hello, When I try and RSH/RLOGIN onto a box with user root, I get the prompt but the username/password combination NEVER work. I have the password up properly on the host machine. Does rsh/rlogin not make use of ./etc/passwd and /etc/shadow? (1 Reply)
Discussion started by: mojoman
1 Replies

10. AIX

Help with rsh problem

Hi all, just after a bit of help.. I am attempting to read in the contents of a flat text file from one system to another using 'rsh', i have this setup over around 15 machines and it works for them all except one. On this one machine it just reads in a blank line for some reason. The machine... (21 Replies)
Discussion started by: forefather1977
21 Replies
ntpdc(8)						      System Manager's Manual							  ntpdc(8)

Name
       ntpdc - monitor operation of the NTP daemon, ntpd

Syntax
       /usr/etc/ntpdc [ -n ][ -v ] host1 | IPaddress1 ...

Description
       The  command sends a query to the daemon running on each of the hosts listed on the command line.  The daemon on each responding host sends
       information about the current calculated offset between its time and the time of each of its NTP servers or peers.  The command formats the
       information on the standard output.

       You  can specify hosts by either host name or Internet address.	The hosts that you specify must either exist in the file, or in the master
       database, if the database is being served to your system by BIND/Hesiod or Yellow Pages.  The command by default generates a terse,  table-
       style report.  If you specify the option, the command generates a verbose report.

Options
       -n     Prints  Internet	addresses,  instead  of host names, of the servers or peers.  By default, the Internet addresses of the responding
	      hosts and the names of their servers or peers are printed.

       -v     Prints a verbose report for each of the servers or peers of the responding host.

Examples
   Terse Report:
       The following is a typical terse report generated in response to the command:
       % /usr/etc/ntpdc 555.5.55.55
       The host 555.5.55.55  is  an  NTP  client,  with  the  servers  and  specified  in  its	file.	The  information  returned  is	about  and
	    Address	      Strat  Poll Reach Delay  Offset  Disp
       (rem)	 (lcl)
       .server1  555.5.55.55  1      64   377	53.0   -65.0   5.0
       *server2  555.5.55.55  1      256  377	155.0  -4.0    16.0
       +server3  555.5.55.55  2      64   377	16.0   -61.0   3.0

       The fields are interpreted as follows:

       - , + , . or *
	      A  minus	sign  (-), plus sign (+), or dot (.) indicates a pre-configured peer (see the reference page).	The asterisk (*) indicates
	      which pre-configured peer (if any) is currently being used for synchronization.

       (rem)  The remote host name or Internet address of a peer or server of the responding host.

       (lcl)  The Internet address of the responding host that was specified on the command line.

       Strat  The current operating stratum level of the peer or server.  Since the NTP hierarchy can change dynamically the  stratum  levels  may
	      change.  Lower stratum levels correspond to higher accuracy.

       Poll   Current polling interval in seconds for this peer or server.  Polling intervals change dynamically.

       Reach  Reachability in response to the last 8 polls (value of 8-bit shift register with bits entering from the end furthest to the right).

       Delay  The estimated round-trip delay in milliseconds for NTP message exchanges between the responding host and this peer or server.  Delay
	      is calculated from the previous 8 polls.

       Offset The estimated offset between the peer or server's time and the responding host's time in milliseconds.   This  value  is	calculated
	      from the previous 8 polls.

       Disp   The current estimated value of dispersion in milliseconds for this peer's offset/delay pair.

	      Dispersion  is  used by the daemon in the clock selection algorithm.  Increasing values of dispersion are associated with decreasing
	      quality of the estimate.

   Verbose Report:
       When the option is given, a verbose report for each of the servers or peers of each of the hosts specified on the command  line	is  gener-
       ated.

       The following is a typical verbose report generated in response to the following command line:
       % /usr/etc/ntpdc -v 111.11.111.11

       Neighbor address 555.55.5.55 port:123  local address 111.11.1.11
       Reach: 0377 stratum: 2, precision: -7
       dispersion: 2.000000, flags: 1301, leap: 0
       Reference clock ID: [22.22.2.22] timestamp: 7e5aa1a9.2add5d0b
       hpoll: 10, ppoll: 10, timer: 1024, sent: 85 received: 90
       Delay(ms)   20.00  20.00  28.00	29.00  20.00  39.00  29.00  28.00
       Offset(ms)   5.00   6.00   5.00	-1.00  -2.00   0.00   3.00   5.00

	       delay: 20.000000 offset: 5.000000 dsp 2.000000
       --------------------------------------------------------------------

       The fields are interpreted as follows:

       Neighbor address
	      The address and port number of one NTP server, followed by the Internet address of the responding host (local address).

       Reach: Reachability in response to the last 8 polls (value of 8-bit shift register with bits entering from the end furthest to the right).

       stratum:
	      The  current  operating  stratum level of the peer or server.  Since the NTP hierarchy can change dynamically the stratum levels may
	      change.  Lower stratum levels correspond to higher accuracy.

       precision:
	      The precision of this clock, given in seconds as a power of 2.  If precision is equal to -7, that means that the precision is 2**-7,
	      or 1/128 seconds.  The daemon automatically determines the precision of each clock based on the kernel variable

       disp:  The  current  estimated  value of dispersion in milliseconds for this peer's offset/delay pair.  Dispersion is used by the daemon in
	      the clock selection algorithm.  Increasing values of dispersion are associated with decreasing quality of the estimate.

       flags: nn
	      The parameter is used by the daemon clock selection process.

       leap: flag
	      The leap second indicator.  Non-zero if there is to be a leap second inserted in the NTP timescale.  The bits are set  before  23:59
	      on the day of insertion and reset after 00:00 on the following day.

       Reference clock ID: address
	      If  the NTP server is synchronized by a radio/satellite timecode receiver, this field is or If the NTP server is the local reference
	      clock, this field is Finally, this field can be the of the most accurate NTP server currently serving the responding host.

       timestamp: nn
	      The local time, in hex-timestamp format, when the local clock of the server was last updated.

       hpoll: n
	      The host poll interval which is the maximum interval between messages transmitted to the server, in seconds as a power  of  2.   For
	      example, a value of 6 indicates an interval of 64 seconds.

       ppoll: n
	      The  peer poll interval which is the maximum interval between messages sent by the server, in seconds as a power of 2.  For example,
	      a value of 6 indicates an interval of 64 seconds.

       timer: nn
	      The current poll rate in seconds.

       sent: nn
	      The number of NTP packets sent to this server by the responding host.

       received: nn
	      The number of NTP packets received from this server by the responding host.

       Delay and Offset
	      The round-trip delay and estimated clock offset for the last eight NTP packet exchanges.	If there are fewer than eight  valid  sam-
	      ples, the delay field will be zero.

       delay: est-delay offset: est-offset dsp: n
	      Estimated delay, offset, and dispersion calculated from the above 8 samples.  See RFC 1129 for how to calculate the estimated delay,
	      offset, and dispersion.

Diagnostics
       host1: connection refused
       Check whether the daemon is running on

       host2: unknown
       The command cannot resolve the host name Check that exists in the file, or that it exists in the master database, if the database is  being
       served by BIND/Hesiod or Yellow Pages.

       If  a server is listed in the host's file, but does not appear in the report, it is possible that the daemon on the responding host can not
       resolve the server names in the file.  Check that the server exists in the responding host's file or in the master database, if	the  data-
       base is being served to the responding host by BIND/Hesiod or Yellow Pages.

See Also
       ntp.conf(5), ntp(8), ntpd(8)
       RFC 1129--Internet Time Synchronization:  the Network Time Protocol
       Introduction to Networking and Distributed System Services

																	  ntpdc(8)
All times are GMT -4. The time now is 08:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy