Hi, I have recently found a problem in baselayout (baselayout-1.12.10-r5 has it). This is an excerpt from /etc/init.d/clock: elif is_vserver_sys ; then TBLURB="VServer" fakeit=1 elif is_xenU_sys ; then TBLURB="xen" fakeit=1 elif [[ -d /proc/vz ]] ; then TBLURB="VZ" fakeit=1 The script checks if the system is some kind of a virtual server, and skips setting the system time in case it is. The problem here is /proc/vz exists even in VE0 (the host system itself, somewhat similar to Xen's Dom0), but the test is supposed to only catch the case we are inside a container (VPS, VE). This created a big problem on my laptop since I use CLOCK="local" -- somehow when clock starts openvz modules are NOT loaded yet, and then it stops openvz modules are loaded. This leads to 3 hours (my timezone is GMT+3) skew on every reboot. Really really annoying, and I think quite critical. I will attach the patch that fixes the issue. Note that baselayout-2.0.0_rc6 is not vulnerable -- from what I see in its code it does the right checks. Reproducible: Always Steps to Reproduce:
Created attachment 139315 [details, diff] proposed fix (tested on my system) I plea for this fix to be included into next baselayout-1.12 update -- screwing the clock does weird things...
baselayout-1 is not usable in vservers, baselayout-vserver is not supported anymore...
This bug is about host system so it baselayout should work there.
it's already fixed in baselayout-2
added for 1.12.11
