Sponsored Content
Operating Systems Linux Red Hat Hardware and system timing are different Post 302904629 by manjusharma128 on Thursday 5th of June 2014 09:13:06 AM
Old 06-05-2014
Hi Robin,

Thanks for your reply.

1)for hardware clock, I will use cmd :
Code:
hwclock --set --date "05/06/2013 17:34:08"

2) Setting System timing to according to Hardware timing:
Code:
# hwclock -s

or
Code:
# hwclock -hctosys

Please advice either hardwae to system timing copy will be ok or system to hardware timing ok?

3) We have already set the time zone so I will not change it.

4) We have some application running over these system where server1 is master and server2 as slave. kindly also advice that we need to stop out application or without stopping, we can proceed for time change?

5)I checked on the internet and mentiond like hardware clock always keep running even after the server is in shutdown status while system clock depends on kernal. once linux OS is shutdwon then system clock stop running.

Kindly Advice...

Last edited by Franklin52; 06-05-2014 at 11:10 AM.. Reason: Please use code tags
 

9 More Discussions You Might Find Interesting

1. Solaris

What command to check system hardware

What command can I run on a Solaris 8 server to check the hardware (ie number of processors, speed of processors, installed memory etc). (4 Replies)
Discussion started by: soliberus
4 Replies

2. UNIX for Advanced & Expert Users

scp timing out

having problems using scp in that during peak hours it appears to time out. anyone have similar experiences? any thoughts regarding a solution... (1 Reply)
Discussion started by: jph
1 Replies

3. Programming

timing your functions

hi everyone. If you have a function created in your code and you want to find out how long it takes for it to run you can use a struct called gettimeofday(). so lets say we have a function like this int myfunction (int r) { /*some math calculations*/ return answer; } How do i set up... (3 Replies)
Discussion started by: bebop1111116
3 Replies

4. Solaris

basic hardware & system requirements for solaris 10

hi all, i want to setup a solaris10 lab for 50 trainees. kindly let me know all the basic hardware & system requirements for the lab . with regards, Raj (5 Replies)
Discussion started by: rajp_8007
5 Replies

5. AIX

System P hardware

hello everybody, Is there any training to get deep knowledge an hands on lab with system p hardware firmware microcode upgrading etc... thanks in advance (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies

6. Shell Programming and Scripting

Timing a script

i have a very big script i have that i'd like to add a timeout to. this script runs on a several remote host. i update this script with timeout clause and then copy it over to all the hosts on which it is currently on. basically, i want the timeout to make the script abort/exit if it's... (1 Reply)
Discussion started by: SkySmart
1 Replies

7. Solaris

Manufacturer name of computer system(hardware) , processor

Hi All, Can someone let me know the method or set of commands by which i can retrive manufacturer name of computer system (hardware of machine ) and manufacturer of processor. i get below information when fired psrinfo command : psrinfo -vp The physical processor has 1 virtual processor... (6 Replies)
Discussion started by: omkar.jadhav
6 Replies

8. UNIX for Advanced & Expert Users

Linux Command To Find the System Configuration And Hardware Information

Hello guys. I wanted to find the System Configuration and Hardware Information on one of my servers. Here is part of the cpu info: CPU core info: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 44 model name : Intel(R) Xeon(R) CPU... (2 Replies)
Discussion started by: Ymir
2 Replies

9. SCO

Need Help Installing Legacy System on Newer Hardware

We have a legacy software application that runs on SCO OpenServer 5.0.6, and the current server (built around 2003-04) is still running. I have been attempting to upgrade the hardware, to hopefully increase the time that we will have access to the data in this system, but am running into an... (13 Replies)
Discussion started by: spock9458
13 Replies
VOS_CHANGELOC(1)					       AFS Command Reference						  VOS_CHANGELOC(1)

NAME
vos_changeloc - Change a volume's entry in the VLDB SYNOPSIS
vos changeloc [-server] <new server name> [-partition] <new partition location> [-id] <volume name or ID> [-cell <cell name>] [-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve] [-help] vos changel [-s] <new server name> [-p] <new partition location> [-i] <volume name or ID> [-c <cell name>] [-noa] [-l] [-v] [-e] [-nor] [-h] DESCRIPTION
The vos changeloc command changes the location of a volume in the Volume Location Database (VLDB) without needing to contact the original file server on which the volume was hosted. This is useful when a file server has gone down permanently and the data that was stored on that server has been moved to a new file server with a different name and IP address (perhaps by mounting the same /vicepX partitions on a different host). After moving the data and running vos changeloc, run vos syncvldb and then vos syncserv against the new server to ensure full synchronization of the VLDB with the file server. In essence, vos changeloc performs the same operations on the VLDB as vos move, but it does NOT move the data from one server's file system to another. CAUTIONS
Using vos changeloc changes the VLDB without modifying the file server data, so it inherently causes the VLDB to be out of sync with the data on the servers. It should only be used when recovering from server failure. If the servers are on-line, vos move should be used instead. It is highly recommended that vos syncvldb and vos syncserv be run after using the vos changeloc command to ensure properly synchronization of the VLDB with the file servers. OPTIONS
vos changeloc takes the following options: -server <new server name> Specifies the new server where the VLDB should believe the volume resides. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1). -partition <partition name> Specifies the partition where the VLDB should believe the volume resides. Provide the -server argument along with this one. Provide the partition's complete name with preceding slash (for example, "/vicepa") or use one of the three acceptable abbreviated forms. For details, see vos(1). -id <volume name or ID> Specifies the name or volume ID number on which to operate. -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1). -noauth Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1). -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1). -verbose Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear. -encrypt Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. -noresolve Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
vos changeloc shows a brief message upon completion: Changed location to server2 /vicepa for volume user.jdoe EXAMPLES
The following command changes the location of the "user.jdoe" volume to be /vicepa on the file server machine "server2" while being verbose: % vos changeloc server2 a user.jdoe -verbose done Changed location to server2 /vicepa for volume user.jdoe The following command changes the location of the "user.jdoe" volume to be /vicepa on "server1" without being verbose: % vos changeloc server1 a user.jdoe Changed location to server1 /vicepa for volume user.jdoe PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root". SEE ALSO
vos(1), vos_move(1), vos_syncserv(1), vos_syncvldb(1) COPYRIGHT
Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com> This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS. OpenAFS 2012-03-26 VOS_CHANGELOC(1)
All times are GMT -4. The time now is 04:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy