Same for me....
workaround:
replace
/bin/cp -fp ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
with
/bin/cp -f ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
and
/bin/cp -fp ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
with
/bin/cp -f ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
in put_param() resp. put_param2() in /etc/sysconfig/vz-scripts/dists/scripts/functions. This will touch /etc/hosts and /etc/sysconfig/network each time you start the VPS and modify the access time (filesystem inside the VPS); I can live with that ![Wink](images/smiley_icons/icon_wink.gif)
Looks like there is something fishy with the cooperation of the /bin/cp from FC5 and OpenVZ framework.
[Updated on: Thu, 30 March 2006 11:35]
Report message to a moderator