| View previous topic :: View next topic |
| Author |
Message |
unfmachine
n00b
Joined: 05 Mar 2017
Posts: 20
|
 Posted: Sat Mar 11, 2017 9:38 pm Post subject: still getting Clock skew detected even after fix |
 |
|
Hello,
I still keep getting the
| Code: | | * Clock skew detected with `/etc/init.d/localmount' |
error when booting my machine even after doing the following fix :
| Code: |
(as root)
# cd /
# touch currtime
# find . -cnewer /currtime -exec touch {} \; |
This fix worked when I installed on hardware but I'm running Gentoo in a virtualbox environment this time just in case that is useful to anyone.
Thanks
:Edited to make more sense:
Last edited by unfmachine on Sat Mar 11, 2017 11:24 pm; edited 1 time in total |
|
| Back to top |
|
 |
khayyam
Watchman
Joined: 07 Jun 2012
Posts: 6227
Location: Room 101
|
| Posted: Sat Mar 11, 2017 9:56 pm Post subject: Re: still getting Clock skew detected even after fix |
|
|
| unfmachine wrote: | | Code: | | * Clock skew detected with `/etc/init.d/localmount' |
|
unfmachine ... run 'rc-update -u', that should resolve the issue.
| (as root): | $ cd /
$ touch currtime
$ find . -cnewer /currtime -exec touch {} \; |
If you use '#' then we would know which UID (root shell's get '#' at the end of the prompt, whereas users get '$', in bash anyway). Anyhow, you probably shouldn't do this as these files will now show as being modified if equerying, eg:
| Code: | | # for p in $(qlist -IC) ; do qcheck $p ; done |
best ... khay |
|
| Back to top |
|
|
unfmachine
n00b
Joined: 05 Mar 2017
Posts: 20
|
| Posted: Sat Mar 11, 2017 11:23 pm Post subject: |
|
|
Thank you!
Problem FIXED!
This forum rocks!
 |
|
| Back to top |
|
|
|
Kernel & Hardware
