Corey Wright wrote:
On Mon, 22 May 2006 10:29:20 -0400
Fareha Shafique <[EMAIL PROTECTED]> wrote:
i assume you are following the process outlined on
http://linux-vserver.org/alpha+util-vserver under "vhashify".
I just wanted to make sure hashify only unifies rpm packages, right?
no. vhashify (the helper application called with "vserver <name> hashify")
has no knowledge of the rpm database and what files are installed by rpm
and which are unique to the specific vserver (whether generated by an rpm
post-installation script or manually created by the user).
Any
other files I want to unify I will have to manually hardlink them?
no. when you run vhashify it creates hardlinks
within /etc/vservers/.defaults/apps/vunify/hash/0 to all files that are not
explicitly excluded within /usr/lib/util-vserver/defaults/vunify-exclude
(well, that's the file within the debian package; location may vary).
I checked /etc/vservers/.defaults/apps/vunify/hash/0 and it consists of
a bunch of directories. At the lowest level, each directory consists of
one file...the purpose of which i do not understand. Any help will be
appreciated.
again, all files are "unified" that are not explicitly excluded.
here's something i had to learn the hard way: you can specify exclusions
for a specific vserver, but the vserver-specific exclusions are
supplementary, not complimentary. so when you
create /etc/vservers/<name>/apps/vunify/exclude it's best to begin that
file with a copy of /usr/lib/util-vserver/defaults/vunify-exclude.
again, if a vserver-specific exclusion list exists, then the default
exclusion list is totally disregarded, and only the vserver-specific
exclusion list is consulted when running vhashify on that vserver.
Thanks.
-FS
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
