Hi there ...

According to Kir's Mail "exec early script at start" from January
the 16th (*1), a file called /etc/vz/conf/9.start should be run
as soon as VE no 9 has been started.

*1) http://openvz.org/pipermail/devel/2008-January/010396.html

I can confirm this for .mount and .umount, but not for .start
and/or .stop. Is the mechanism broken or has it been removed?

I'm Running openvz on a Debian etch 64Bit box, my vzctl is
version 3.0.22-1dso1, installed via apt:

deb http://download.openvz.org/debian-systs etch openvz

Thomas

Thomas Sattler wrote:
> Hi there ...
>
> According to Kir's Mail "exec early script at start" from January
> the 16th (*1), a file called /etc/vz/conf/9.start should be run
> as soon as VE no 9 has been started.
>
> *1) http://openvz.org/pipermail/devel/2008-January/010396.html
>
> I can confirm this for .mount and .umount, but not for .start
> and/or .stop. Is the mechanism broken or has it been removed?

I have just rechecked that, it is working for me (vzctl-3.0.21, 
pre-release version), see:

dionysos ~ # ls -l /etc/vz/conf/1002.start
-rw-r--r-- 1 root root 46 Mar 12 18:35 /etc/vz/conf/1002.start

dionysos ~ # cat /etc/vz/conf/1002.start
#!/bin/sh

echo "=== start script called ==="

dionysos ~ # vzctl start 1002
Starting VE ...
VE is mounted
WARNING: IPv6 support is disabled
Adding IP address(es):
Setting CPU units: 1000
Configure meminfo: 35000
=== start script called ===
VE start in progress...

dionysos ~ # vzctl restart 1002
Restarting VE
Stopping VE ...
VE was stopped
VE is unmounted
Starting VE ...
VE is mounted
WARNING: IPv6 support is disabled
Adding IP address(es):
Setting CPU units: 1000
Configure meminfo: 35000
=== start script called ===
VE start in progress...