Hi Kir
We are talking about 2.6.32.
The "kernel guys" you are referring to, do you mean the Debian kernel guys?
If so, we need to contact them so they take the latest version. They
will not do that automatically as Debian is frozen now.
Best regards,
// Ola
Quoting "Kir Kolyshkin" <k...@openvz.org>:
On 09/04/2010 02:09 AM, Ola Lundqvist wrote:
Hi Kir
I saw that you had fixed the alternative solution to have it in the
kernel. However that will not be available for Debian. Or will it?
What kernel are we talking about? If 2.6.32 than after kernel guys
will suck in
v2.6.32-dobrovolskiy.1 the required stuff will be there.
Best regards,
// Ola
On Mon, Aug 30, 2010 at 02:41:12PM +0400, Kir Kolyshkin wrote:
On 08/30/2010 11:57 AM, Ola Lundqvist wrote:
Hi Kir, Christian
Should we simply remove this file? Or should we simply add something
dummy to it?
I do not see where do we create this file -- anywhere in vzctl sources.
We create S00vzreboot in rc6.d, this is needed for reboot mark
(/reboot file) to be created when runlevel 6 is reached. In case
a container is restarted from within (i.e. container's root run 'reboot')
the host system script (vzreboot, run from cron every 5 minutes)
finds this file and restarts the container.
I am going to implement an alternative solution -- the kernel will send
stop/reboot events to the daemon, which will do the needed stuff.
This will render the above functionality redundant and so it will be
removed.
For now, I guess, we can reimplement this S00vzreboot as a proper
symlink, this requires some changes in src/lib/script.c. There is an
open bug for it, http://bugzilla.openvz.org/1423
Corrected a similar bug in #594783 just an hour ago.
// Ola
Quoting "Christian Hofstaedtler"<c...@zeha.at>:
Hi Ola, Kir,
the sysv-rc upgrade today migrated my installation to 'dependency
based booting', complained quite a bit about K00vzreboot, but went
on with the migration. It left this state:
# ls -CF1 /etc/rc6.d
K00vzreboot*
K01nullmailer@
K01pdns@
K01unattended-upgrades@
K01urandom@
K02sendsigs@
K03rsyslog@
K04hwclock.sh@
K04umountnfs.sh@
K05networking@
K06ifupdown@
K07umountfs@
K08umountroot@
K09reboot@
README
If I'm not mistaken this will start vzreboot first, and then the other
shutdown scripts will never run. If this is the case, this is a critical
issue.
After restarting the CT, I now have these scripts:
# ls -CF1 /etc/rc6.d
K00vzreboot*
K01nullmailer@
K01pdns@
K01unattended-upgrades@
K01urandom@
K02sendsigs@
K03rsyslog@
K04hwclock.sh@
K04umountnfs.sh@
K05networking@
K06ifupdown@
K07umountfs@
K08umountroot@
K09reboot@
README
S00vzreboot*
This can't be correct ;)
Christian
--
christian hofstaedtler
--
--- Inguza Technology AB --- MSc in Information Technology ----
/ o...@inguza.com Annebergsslingan 37 \
| o...@debian.org 654 65 KARLSTAD |
| http://inguza.com/ Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
