Re: [Vserver] V_xxxx not running ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benoît des Ligneris wrote: > Hello, > > Well, I think that this is a useful tool for the vserver project. > > We are using v_portmap as well as some others v_* scripts. After having > installed several vserver hosts I think it is much more easy to modify > the services than to go after every application and modify one or > several configuration file. > > Also, it is easy to check the existing services running on a given host > and to create the v_* scripts in order to make sure that no port > conflict will occur between the vservers and the host. This is a general > solution to this kind of problem whereas fixing each application > individually can be, IMHO, a pain... Then I would suggest that perhaps you are running too many services on the host? My philosophy is to keep the host as minimal as possible and run everything inside a guest (generally one guest per service). The only two services I run on my hosts are sshd and ntpd. Every other service that I might want to run on the host can be run inside a guest. I run sshd on all my machines on a non-standard port ( for hosts and 222 for guests) as a way of stopping my logs from filling up with door-knock attempts which also solves the port conflict issue. Regards Darryl -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFC5IWE/XQ6DbmPjokRAqs6AJ9Nr6tZfvzS9sMuPxhjh256gy270ACfUDMg J4L9YzUCCdOdtdnd1Jegbs8= =JFu7 -END PGP SIGNATURE- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] Install issue with yum - /var/lib/rpm/ ?
Hi, > > Unfortunately, I have some issues with a messages, that > > pops up during installation. > > It's only a message... because yum does not do proper > error-handling, the installation will succeed nevertheless. Hmm... But the .rpmdb directory inside the guest os is empty when the yum installation finishes ? Should it be like that ? Regards, /Brian ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Install issue with yum - /var/lib/rpm/ ?
[EMAIL PROTECTED] (Brian Ipsen) writes: > I'm trying to install a WBEL4 client OS via yum (the RPM list has been > attached here). The rpm list does not matter (and is ignored by the '-m yum' method). > Unfortunately, I have some issues with a messages, that pops up during > installation. It's only a message... because yum does not do proper error-handling, the installation will succeed nevertheless. > I'm not quite sure, whether this warnings/errors shows up due to > missing dependency settings in the RPM - or it could be an issue with > installing via RPM... This happens because the rpm package has bad assumptions regarding the availability of the rpmdb in %scriptlets. Because of security reasons, this rpmdb is hidden and 'chown /var/lib/rpm/[A-Z]*' will not find a file where it can operate on. > The errors I get are: > > /bin/chown: cannot access `/var/lib/rpm/[A-Z]*': No such file or directory A workaround would be, to add a | touch "$vdir"/.rpmdb/FORTYTWO or (better, but untested) | ( cd "$vdir" && $_CHROOT_SH append /var/lib/rpm/FORTYTWO pgphQTf9KYy7s.pgp Description: PGP signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Install issue with yum - /var/lib/rpm/ ?
Hi, I'm trying to install a WBEL4 client OS via yum (the RPM list has been attached here). Unfortunately, I have some issues with a messages, that pops up during installation. I'm not quite sure, whether this warnings/errors shows up due to missing dependency settings in the RPM - or it could be an issue with installing via RPM... The errors I get are: /bin/chown: cannot access `/var/lib/rpm/[A-Z]*': No such file or directory I've located this to ve caused by the post-install script from the rpm package: /sbin/ldconfig # Establish correct rpmdb ownership. /bin/chown rpm.rpm /var/lib/rpm/[A-Z]* # XXX Detect (and remove) incompatible dbenv files during db-4.2.52 upgrade. # XXX Removing dbenv files in %post opens a lock race window, a tolerable # XXX risk compared to the support issues involved with upgrading Berkeley DB. [ -w /var/lib/rpm/__db.001 ] && /usr/lib/rpm/rpmdb_stat -CA -h /var/lib/rpm 2>&1 | grep "db_stat: Program version 4.2 doesn't match environment version" 2>&1 > /dev/null && rm -f /var/lib/rpm/__db* exit 0 Anyone ? /Brian indexhtml-4-2.WB2 rootfiles-8-1 filesystem-2.3.0-1 termcap-5.4-3 glibc-common-2.3.4-2 audit-0.5-1 bzip2-libs-1.0.2-13 device-mapper-1.00.19-2 e2fsprogs-1.35-11.6.EL4 ethtool-1.8-4 gdbm-1.8.0-24 hdparm-5.7-2 libattr-2.4.16-3 libcap-1.10-20 libsepol-1.1.1-2 libstdc++-3.4.3-9.EL4 gmp-4.1.4-3 mingetty-1.07-3 bash-3.0-19.2 ncurses-5.4-13 net-tools-1.60-37 perl-5.8.5-12.1 popt-1.9.1-7_nonptl.WB2 rpmdb-whitebox-4-0.20050504 slang-1.4.9-8 usbutils-0.11-6.1 vim-minimal-6.3.046-0.40E.4 whitebox-release-4-2.WB2 file-4.10-2 cpio-2.5-7.EL4.1 ed-0.2-36 gawk-3.1.3-10.1 coreutils-5.2.1-31 grub-0.95-3.1 krb5-libs-1.3.4-12 openssl-0.9.7a-43.1 readline-4.3-13 pyxf86config-0.3.19-1 rpm-libs-4.3.3-7_nonptl.WB2 shadow-utils-4.0.3-41.1 dbus-glib-0.22-11.EL nscd-2.3.4-2 sysklogd-1.4.1-26_EL cracklib-2.7-29 pam-0.77-65.1 policycoreutils-1.18.1-4 SysVinit-2.85-34 lvm2-2.00.31-1.0.RHEL4 hal-0.4.2-1.EL4 cyrus-sasl-2.1.19-5.EL4 kudzu-1.1.95.8-1 kernel-2.6.9-5.EL libuser-0.52.5-1 prelink-0.3.3-0.EL4 usermode-1.74-1 system-config-mouse-1.2.9-1 mailcap-2.1.17-1 rmt-0.4b37-1 specspo-9.0.92-1.3.WB1 bluez-hcidump-1.11-1 dosfstools-2.8-15 finger-0.17-26 hesiod-3.0.2-30 attr-2.4.16-3 libgpg-error-1.0-1 libjpeg-6b-33 lrzsz-0.12.20-19 mailx-8.1.1-33 bzip2-1.0.2-13 anacron-2.3-32 mt-st-0.8-1 mtr-0.54-10 pam_smb-1.1.7-5 pax-3.0-9 aspell-en-0.51-11 numactl-0.6.4-1.13 logrotate-3.7.1-2 rdate-1.4-2 rsh-0.17-25.1 schedutils-1.4.0-2 netconfig-0.8.21-1 setuptool-1.17-2 symlinks-1.2-22 htmlview-3.0.0-8 tcp_wrappers-7.6-37.2 tmpwatch-2.9.1-1 unix2dos-2.2-24 wireless-tools-27-0.pre25.4.EL4 zip-2.3-27 freetype-2.1.9-1 binutils-2.15.92.0.2-10.EL4 gpm-1.20.1-66 groff-1.18.1.1-3 krb5-workstation-1.3.4-12 libtiff-3.6.1-8 libxslt-1.1.11-1 m4-1.4.1-16 man-1.5o1-9 irda-utils-0.9.16-3 nano-1.2.4-1 bind-libs-9.2.4-2 cups-libs-1.1.22-0.rc1.9.6 pdksh-5.2.14-30 psacct-6.3.2-31 ftp-0.17-22 parted-1.6.19-1.EL libxml2-python-2.6.16-6 rhnlib-1.8-6.p23 lockdev-1.0.1-3 rpm-python-4.3.3-7_nonptl.WB2 stunnel-4.05-3 sysreport-1.3.13-1.WB1 time-1.7-25 wget-1.9.1-17 xmlsec1-openssl-1.2.6-3 xorg-x11-Mesa-libGL-6.8.1-23.EL.WB1 pam_ccreds-1-3 acpid-1.0.3-2 bluez-utils-2.10-2.1 dhclient-3.0.1-38_EL4 ipsec-tools-0.3.3-6 kernel-utils-2.4-13.1.48 iptstate-1.3-4 mkbootdisk-1.5.2-1 autofs-4.1.3-67 nss_ldap-226-1 openssh-clients-3.9p1-8.RHEL4.1 pciutils-2.1.99.test8-3 portmap-4.0-63 ppp-2.4.2-6.4.RHEL4 rp-pppoe-3.5-22 mdadm-1.6.0-2 tcpdump-3.8.2-7 system-config-network-tui-1.3.22-1 vixie-cron-4.1-20_EL wvdial-1.54.0-3 cups-1.1.22-0.rc1.9.6 ypbind-1.17.2-3 comps-4.0.whitebox-0.20050504.WB1 hwdata-0.146.1.EL-1 libgcc-3.4.3-9.EL4 setup-2.5.37-1.1 basesystem-8.0-4 tzdata-2004e-2 glibc-2.3.4-2 beecrypt-3.1.0-6 chkconfig-1.3.11.2-1 dmraid-1.0.0.rc5f-rhel4.1 elfutils-libelf-0.97-5 expat-1.95.7-4 glib2-2.4.7-1 iputils-20020927-16 libacl-2.2.23-5 libselinux-1.19.1-7 checkpolicy-1.17.5-1 db4-4.2.52-7.1 libtermcap-2.0.8-39 mktemp-1.5-20 iproute-2.6.9-3 less-382-4 pcre-4.5-3 perl-Filter-1.30-6 psmisc-21.4-4 setserial-2.17-17 newt-0.51.6-5 hotplug-2004_04_01-7.2 whitebox-logos-1.1.25-1.WB1 zlib-1.2.1.2-1 info-4.7-5 diffutils-2.8.1-12 findutils-4.1.20-7 grep-2.5.1-31 ash-0.3.8-20 gzip-1.3.3-13 module-init-tools-3.1-0.pre5.3 procps-3.2.3-7EL python-2.3.4-14.1 rhpl-0.148.2-1 sed-4.1.2-4 dbus-0.22-11.EL MAKEDEV-3.15-2 rpm-4.3.3-7_nonptl.WB2 tar-1.14-4 cracklib-dicts-2.7-29 authconfig-4.6.5-3.1 setools-1.5.1-5 util-linux-2.12a-16.EL4.6 udev-039-10.8.EL4 initscripts-7.93.11.EL-1.WB1 cyrus-sasl-md5-2.1.19-5.EL4 mkinitrd-4.1.18-2.WB1 openldap-2.2.13-2 passwd-0.68-10 selinux-policy-targeted-1.17.30-2.52.1 kbd-1.12-2 cryptsetup-0.1-4 man-pages-1.67-3 dump-0.4b37-1 bluez-libs-2.10-2 dos2unix-3.1-21 eject-2.0.13-11 glib-1.2.10-15 lha-1.14i-17 acl-2.2.23-5 libgcrypt-1.2.0-3 libusb-0.1.8-3 lsof-4.72-1 bluez-bluefw-1.0-6 crontabs-1.10-7 nc-1.10-22 pam_passwdqc-0.7.5-2 patch-2.5.4-20 aspell-0.50.5-3.fc3 fbset-2.1-17 desktop-file-utils-0.9-2 procmail-3.22-14 rdist-6.
Re: [Vserver] V_xxxx not running ?
Hello, Well, I think that this is a useful tool for the vserver project. We are using v_portmap as well as some others v_* scripts. After having installed several vserver hosts I think it is much more easy to modify the services than to go after every application and modify one or several configuration file. Also, it is easy to check the existing services running on a given host and to create the v_* scripts in order to make sure that no port conflict will occur between the vservers and the host. This is a general solution to this kind of problem whereas fixing each application individually can be, IMHO, a pain... Ben Enrico Scholz a écrit : > [EMAIL PROTECTED] (Herbert Poetzl) writes: > > >>>I will fix it, although the v_* scripts will disappear soon. >> >>and be replaced by? > > > nothing ;) > > I do not see much sense in these scripts. Most affected applications > (httpd, named, sendmail, ssh, xinetd) can be configured with "native" > methods to listen on a limited set of interfaces. 'portmap' is the only > daemon where v_portmap might be useful, but it is not used very much > today resp. only by programs which can run in the host only. And the > missing reports about the broken startup order in v_portmap tells me, > that this script is unused. ;) > > > > Enrico > > > > > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver -- Benoît des Ligneris Ph. D. Président / C.E.O. Revolution Linux http://www.revolutionlinux.com/ Toutes les opinions et les prises de position exprimées dans ce courriel sont celles de son auteur et ne représentent pas nécessairement celles de Révolution Linux. Any views and opinions expressed in this email are solely those of the author and do not necessarily represent those of Revolution Linux. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] V_xxxx not running ?
[EMAIL PROTECTED] (Herbert Poetzl) writes: >> I will fix it, although the v_* scripts will disappear soon. > > and be replaced by? nothing ;) I do not see much sense in these scripts. Most affected applications (httpd, named, sendmail, ssh, xinetd) can be configured with "native" methods to listen on a limited set of interfaces. 'portmap' is the only daemon where v_portmap might be useful, but it is not used very much today resp. only by programs which can run in the host only. And the missing reports about the broken startup order in v_portmap tells me, that this script is unused. ;) Enrico pgppyQ8ihXjgS.pgp Description: PGP signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
