WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Unable to set system clock on domU

On Tuesday, 17 February 2009 13:54:12 +0100,
Thomas Halinka wrote:

> Hi Daniel,

Hi Thomas.

> > On Tuesday, 17 February 2009 14:45:45 +0700,
> > Fajar A. Nugraha wrote:
> > 
> > > > dom0 synchronizes its clock using ntpdate and
> > > > /proc/sys/xen/independent_wallclock is set to 0 on dom0. what can be
> > > > happening?
> >  
> > > Set it to "1".
> > 
> > I tried setting /proc/sys/xen/independent_wallclock to "1" and booting
> > again the domU, but I obtain the same message during boot.
 
> you need to remove hwclock.sh from bootup
> 
> update-rc.d -f hwclock.sh remove
> 
> should do this job for you....

I've removed the symlinks to the script hwclock.sh but I continue
obtaining the warning, although now only it appears a single time
instead of twice like before. I consider that it will be because another
script is being executed on boot and it invokes to hwclock:

# ll /etc/init.d/hw*
-rwxr-xr-x 1 root root 4546 feb 17 19:12 /etc/init.d/hwclockfirst.sh
-rw-r--r-- 1 root root 4521 abr 28  2008 /etc/init.d/hwclock.sh

He is peculiar that only hwclockfirst.sh has execution permission.

Removing these two scripts of boot can cause some collateral effect?


Thanks for your reply.

Regards,
Daniel
-- 
Daniel Bareiro - System Administrator
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users