Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 14 Jan 2010 19:43:24 +0300
From: Solar Designer <>
Subject: Re: Network unreachable from inside Owl CT

On Mon, Dec 14, 2009 at 05:04:47PM +0700, Ihsan Sabri wrote:
> You and GalaxyMaster are right. Renaming
> Owl-current-20091129-x86_64.tar.gz to owl-current-20091129-x86_64.tar.gz and
> use owl-current-20091129-x86_64 as ostemplate works great. No more
> workaround nedeed.

I've just made the above rename official - that is, we will be using
all-lowercase "owl" in our OpenVZ template filenames such that vzctl
uses owl.conf for them by default.

If anyone is curious, this works due to partial template name matching
implemented in vzctl-3.0.23/src/lib/dist.c: get_dist_conf_name().
With owl-current-20091129-x86_64, it will look for
owl-current-20091129-x86_64.conf, owl-current-20091129.conf,
owl-current.conf, and finally owl.conf - in that order.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.