dtsdate(1m) [hpux man page]

dtsdate(1m)															       dtsdate(1m)

NAME

       dtsdate - Sets local clock from a remote dtsd server host

SYNOPSIS

       dtsdate [-q] [-s] [-u] remote_host [nsecs]

ARGUMENTS

       Queries	the difference in time between the local host and the remote host, but does not change the local clock.  The returned result (2 if
       the time would have been reset, 1 if there was an error, and 0 otherwise) can be used by a script to determine what action to take.  Causes
       dtsdate	to  work  silently,  without  showing  the time.  Shows the time in UTC, rather than in the current time zone.	The name or the IP
       address of a remote host that has a dtsd server.  An integer giving the number of seconds by which the remote and local host times can dif-
       fer,  without  the  local host's clock being reset.  If nsecs is 0, or if it is not specified, it is treated as if it were extremely large,
       and no resetting occurs.

DESCRIPTION

       The dtsdate command sets the local clock of a system to be the same as the host remote_host, running a dtsd server.  The purpose of dtsdate
       is  to ensure that clock skew is minimized at initial cell configuration or at host instantiation, because it is difficult to start DCE and
       its components if the skew is too great.

       Clocks among all DCE components must be within five minutes of each other, to prevent failure of CDS and of security.  Some DCE	components
       have even more stringent requirements.  For instance, a DFS file server cannot start if its local host differs from other DFS hosts by more
       than ten seconds.

       The dtsdate command can be used for adjusting a clock backwards, before DCE is running on a host.  Adjusting a clock backwards while DCE is
       running can cause many difficulties, because security and file system software generally require system time to increase monotonically.

NOTES

       The  remote  host  must be running as a DTS server.  This means that the dtsd on that system must have registered the DTS management inter-
       face, because dtsdate uses the management call to get the current time from that host.

       For dtsdate to be able to set the clock, it must run as a privileged user (root).

EXIT VALUE

       If the -q argument is given, dtsdate returns 2 if the remote time and local time differ by more than nsecs, 1 if there was an error, and  0
       otherwise.

       If the -q argument is not given, dtsdate returns 1 if there was an error, and 0 otherwise.

EXAMPLES

       With only the host argument:
	 dtsdate remotehost

       dtsdate prints out the time on the remote host.

       In this example:
	 dtsdate -s -q remotehost 10

       dtsdate does not print out the remote host's time.  If the times differ by more than 10 seconds, it returns the value of 1, otherwise 0.

       In the next example:
	 dtsdate  -s  remotehost  10  dtsdate  sets  the  clock  if  it differed from the remote clock by more than 10 seconds.  It does this work
       silently, because of the -s option.

       The following example shows a shell script that uses the return value of dtsdate:
	 dtsdate -s -q remhost 10
	 result = $?
	 if [ $result -eq 0 ] ; then
	     echo "Time is within tolerence."
	 elif [ $result -eq 1 ] ; then
	     echo "Could not contact remote host." >&2
	 else				   # result = 2
	   if dtsdate remhost 10; then	   # it failed!
	       echo "Could not set the clock." >&2
	   fi
	 fi

RELATED INFORMATION

       Commands: dtsd(1m)

																       dtsdate(1m)

rsh(1)							      General Commands Manual							    rsh(1)

NAME

       rsh - Executes the specified command at the remote host or logs into a remote host

SYNOPSIS

       rsh [-dn] [-l user] remote_host [command] [argument...]

       The remote shell command (rsh) executes command at the remote_host, or, if no command is specified, logs into remote_host.

OPTIONS

       Turns  on  socket  debugging (using setsockopt()) on the TCP sockets used for communication with the remote host.  Specifies that rsh is to
       log into the remote host as user instead of the local username.	If this option is not specified, the local and remote  usernames  are  the
       same.   Specifies  that	rsh is to ignore input from STDIN.  Use this option if you put rsh in the background without redirecting its input
       away from the terminal. If you do not use this option in this situation, rsh blocks even if no reads are posted by the remote command.

DESCRIPTION

       The rsh command sends standard input from the local host to the remote command and receives standard output and	standard  error  from  the
       remote command.	If you do not specify a command, rsh executes rlogin instead.

       If  you do not specify the -l option, the local username is used at the remote host.  If -l user is entered, the specified username is used
       at the remote host.  In either case, the remote host allows access only if at least one of the following conditions is satisfied: The local
       user  ID  is  not superuser, and the name of the local host is listed as an equivalent host in the remote /etc/hosts.equiv file.  If either
       the local user ID is superuser or the check of /etc/hosts.equiv fails, the remote user's home directory must contain a  $HOME/.rhosts  file
       that lists the local host and username.

       For  security  reasons, any $HOME/.rhosts file must be owned by either the remote user or the root user, and should have permissions set to
       600 (read and write by owner only).

       In addition to the preceding conditions, rsh also allows access to the remote host if the remote user account  does  not  have  a  password
       defined.  However, for security reasons, use of a password on all user accounts is recommended.

       While  the  remote  command  is	executing,  pressing the Interrupt, Terminate, or Quit key sequences sends the corresponding signal to the
       remote process.	However, pressing the Stop key sequence stops only the local process. Normally, when the remote  command  terminates,  the
       local rsh process terminates.

       To  have  shell metacharacters interpreted on the remote host, place the metacharacters inside  (double quotes). Otherwise, the metacharac-
       ters are interpreted by the local shell.

RESTRICTIONS

       The rsh command is confused by output generated by commands in a file on the remote host.  In particular, the messages, where are you?  and
       stty: Can't assign requested address can result if output is generated by the startup file.

EXAMPLES

       In  the	following  examples, the local host host1 is listed in the /etc/hosts.equiv file at the remote host host2.  To check the amount of
       free disk space on the remote host host2, enter: $ rsh host2 df To append a remote file to another file on the remote host,  place  the	>>
       metacharacters  in   (double quotes): $ rsh host2 cat test1 ">>" test2 To append a remote file at the remote host to a local file, omit the
       double quotes: $ rsh host2 cat test2 >> test3 To append a remote file to a local file and use a remote user's  permissions  at  the  remote
       host, use the -l option: $ rsh host2 -l jane cat test4 >> test5

FILES

       Specifies  remote  hosts  from which users can execute commands on the local host (provided these users have an account on the local host).
       Specifies remote users that can use a local user account.

SEE ALSO

       Commands:  rcp(1), rlogin(1), rshd(8), telnet(1)

       Functions:  rexec(3)

       Files:  rhosts(4)

																	    rsh(1)