Hi Kir
Now I have tested the new kernel. It seems to work find. However I have a
question
about the vzeventd functionality. When I issue the "reboot" command in the vz
container
the VZ stops. It is never started again. Is that intentional or a fault?
Best regards,
// Ola
On Mon, Sep 13, 2010
Hi Christian
Thanks for the help to verify the package.
// Ola
On Mon, Sep 13, 2010 at 06:53:43PM +0200, Christian Hofstaedtler wrote:
> Ola,
>
> Same here, stop/start now properly shuts down all services, etc.
> Still need to wait for the new kernel though.
>
> Christian
>
> * Ola Lundqvist
Ola,
Same here, stop/start now properly shuts down all services, etc.
Still need to wait for the new kernel though.
Christian
* Ola Lundqvist [100910 21:53]:
> Hi Christian and Kir
>
> Now I have verfied that the new vzctl version works well on
> squeeze. Including virtual hosts running squeez
Hi Christian and Kir
Now I have verfied that the new vzctl version works well on
squeeze. Including virtual hosts running squeeze.
I have changed the documentation slightly to reflect this.
I will wait a day or two, but then I will upload a new updated
package with the improved documentation.
Ho
Hi Christian
For the reboot functionality to work, yes you need the new kernel.
However you can already now check whether you see a problem with the
start and stop operations, if it is initiated from outside.
That is, with the current change the following should work.
vzctl start
vzctl sto
On 09/09/2010 12:33 PM, Christian Hofstaedtler wrote:
Ola,
Do I need to have a kernel with vzevent support for this to test?
Chris, this is correct.
If so then I must wait until such a kernel appears in Debian...
Right. Max Attems informed me yesterday that the kernel will be ready
Ola,
Do I need to have a kernel with vzevent support for this to test?
If so then I must wait until such a kernel appears in Debian...
Thanks,
Christian
* Ola Lundqvist [100909 08:06]:
> Hi Christian
>
> I have today uploaded a 3.0.24-4 version with a backport of support
> for this. It is a ra
Hi Ola,
I'll grab this version from incoming.d.o and give it a test.
Thanks!
Christian
* Ola Lundqvist [100909 08:06]:
> Hi Christian
>
> I have today uploaded a 3.0.24-4 version with a backport of support
> for this. It is a rather extensive patch so I would like you to test
> that this actua
Hi Christian
I have today uploaded a 3.0.24-4 version with a backport of support
for this. It is a rather extensive patch so I would like you to test
that this actually works well for you.
I'm eager to get this into squeeze so if you have the possibility to
test this soon that would be really gre
Hi Kir
Quoting "Kir Kolyshkin" :
On 09/06/2010 11:39 AM, Ola Lundqvist wrote:
Hi Kir
We are talking about 2.6.32.
The "kernel guys" you are referring to, do you mean the Debian kernel guys?
yes
If so, we need to contact them so they take the latest version. They
will not do that automati
On 09/06/2010 11:39 AM, Ola Lundqvist wrote:
Hi Kir
We are talking about 2.6.32.
The "kernel guys" you are referring to, do you mean the Debian kernel guys?
yes
If so, we need to contact them so they take the latest version. They
will not do that automatically as Debian is frozen now.
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" :
On 09
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.
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?
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
>
Hi Christian
It looks like there are now kernel support for this so this can be
removed. However This functionality is not available in the kernel
in Debian yet. I have contacted Kir to check how we can sort this out.
Best regards,
// Ola
On Mon, Aug 30, 2010 at 09:04:00AM +0200, Christian Hofs
Hi Ola,
Removing is probably a bad idea, as - as far as I understand it - this would
cause containers to no longer reboot (will shutdown, but won't start up again).
Turning it into the file /etc/init.d/vzreboot with proper headers is probably
the only Debian-ok way to go. I'm unsure how the syml
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
Hi Kir
Will you make this change or should I propose a patch for this?
// Ola
Quoting "Kir Kolyshkin" :
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 fil
Hi Kir, Christian
Should we simply remove this file? Or should we simply add something
dummy to it?
Corrected a similar bug in #594783 just an hour ago.
// Ola
Quoting "Christian Hofstaedtler" :
Hi Ola, Kir,
the sysv-rc upgrade today migrated my installation to 'dependency
based booting',
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@
K
Hi Ola, Kir,
To escape the sysv-rc/insserv problems, I tried migrating to file-rc.
Turns out, file-rc doesn't like the 'regular file in /etc/rc6.d/'
either. Might be because /etc/rcX.d/ is provided by sysv-rc and
removed completely on sysv-rc removal.
Providing a normal /etc/init.d/vzreboot with
Hi Kir
Thanks a lot for this information. I'll add a note about this to the
README.Debian
file so people know about this limitation.
Best regards,
// Ola
On Mon, Apr 05, 2010 at 02:56:54PM +0400, Kir Kolyshkin wrote:
> On 04/03/2010 04:04 PM, Ola Lundqvist wrote:
>> Hi Christian
>>
>> On Sat,
On 04/03/2010 04:04 PM, Ola Lundqvist wrote:
Hi Christian
On Sat, Apr 03, 2010 at 11:13:38AM +0200, Christian Hofstaedtler wrote:
Hi Ola,
* Ola Lundqvist [100402 00:49]:
I have never used insserv myself. Can you send me your
S00vzreboot file? I need to determine why it considers it
Hi Christian
On Sat, Apr 03, 2010 at 11:13:38AM +0200, Christian Hofstaedtler wrote:
> Hi Ola,
>
> * Ola Lundqvist [100402 00:49]:
> > I have never used insserv myself. Can you send me your
> > S00vzreboot file? I need to determine why it considers it to be
> > corrupt.
>
> Squeeze seems to ins
Hi Ola,
* Ola Lundqvist [100402 00:49]:
> I have never used insserv myself. Can you send me your
> S00vzreboot file? I need to determine why it considers it to be
> corrupt.
Squeeze seems to install insserv by default, so this was not my choice ;-)
> From the source in squeeze it looks like it
Hi Christian
I have never used insserv myself. Can you send me your
S00vzreboot file? I need to determine why it considers it to be
corrupt.
>From the source in squeeze it looks like it generates the following file:
#!/bin/bash
> /reboot
And that is about it. It is understandable if insserv cons
Package: vzctl
Version: 3.0.22-14
Severity: normal
Hi Ola,
with a lenny host and a squeeze VE, insserv *inside* the VE complains
that the automatically created vzreboot script is 'corrupt or invalid':
insserv: warning: script is corrupt or invalid: /etc/init.d/../rc6.d/S00vzreboot
This happens
27 matches
Mail list logo
