[Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc
> On Wed, Feb 01, 2006 at 07:48:25AM +0100, Joel Soete wrote: > > Hello Herbert, > > > > The latest test seems always ok (I mean no regression imho) on this > > parisc 32bit up kernel ;-) > > great! > > nitpick: let's prefix the tests with [ARCH] in the future > (for ML postings) to simplify searching ... > Good catch, I will try to take care on next time ;-) > btw, we a planning to support an -m 'mail' option to > send the arch info to the ML in the near future ... > cool ;-) (even thought my compamy fw didn't allow smtp port usage, it would be great to just cut and past the 'template' mail temporary file in the webmail interface of my own isp (obiously company mail box is also forbiden :_( )) [...] > > > > Btw may I ask you to add this -n (i.e. no_color option) to testme. > > That would look like: > > no problem, will put it into the next version ... > Nice :-) Tx, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] tagxid mount option
Herbert Poetzl schrieb: how did you try? (i.e. what filesystem, which partition, what options) /dev/sda1 / ext3 defaults,tagxid,errors=remount-ro 0 1 gives failures on reboot, leaving / unaccessible, I have to boot from cdrom and correct (remove the tagxid option) the fstab. I want to set context disk limits with vdlimit, therefore I need the tagxid mount option, did I get it right? how do I enabled tagxid support? kernel option uid24/gid24 is set. yes, usually it's just a matter of: mount -o tagxid /dev/some /vservers does not work too. gives a german error message, meaning already mounted or invalid option. cu joh. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Herbert Poetzl wrote: > On Wed, Feb 01, 2006 at 01:40:29PM -0500, Micah Anderson wrote: > > Herbert Poetzl wrote: > >>>Btw may I ask you to add this -n (i.e. no_color option) to testme. >>>That would look like: > > >>no problem, will put it into the next version ... > >>thanks, >>Herbert > > I thought that the -n (no_color) option was added after I sent a similar > patch back in October[1]? > > >> yes, it was, but (if you read your mail again) only >> to the testfs.sh script, not the testme.sh one ... /me hits head with hand. micah -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD4SG59n4qXRzy1ioRAsJ/AJ9GiMfPLq1GwiST/Zng1pLiiRnZVQCdF6iY 9faF5SBsx7eSi8ppXLUXpzA= =iGTQ -END PGP SIGNATURE- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?
On Wed, Feb 01, 2006 at 06:29:05PM +0100, Grzegorz Nosek wrote: > Hello all, > > I started playing with vserver unification recently and I'd like to > share my two observations: > > - under Debian (sarge at least) you cannot use the supplied beecrypt2 > packages as they have a slightly different API (changes are subtle > enough that util-vserver will compile but hashcalc will die with a > segmentation fault). Use beecrypt4: > http://prdownloads.sourceforge.net/beecrypt/beecrypt-4.0.0.tar.gz?download good to know ... well a lot of stuff is broken in sarge, hope we can fix that soon ... > - If I modify a file's contents the CoW link is broken properly but > after a chmod or chown the link is not broken and I get -EPERM (as the > files are marked immutable) - is this expected behaviour? In such a > situation the links aren't exactly CoW... interesting observation, well, strictly speaking chmod or chow are no writes, so CoW is not involved, but I will look into extending the CoW behaviour to those operations in the future ... thanks, Herbert > Best regards, > Grzegorz Nosek > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] tagxid mount option
On Wed, Feb 01, 2006 at 03:07:56PM +0100, J.Paechnatz wrote: > got vserver working and running some different machines, debian/ubuntu > mixed. so, nice work guys! thanks! > I could not mount with the tagxid option. how did you try? (i.e. what filesystem, which partition, what options) > system is running on: > > Versions: >Kernel: 2.6.12-joh >VS-API: 0x00020001 > util-vserver: 0.30.208; Dec 3 2005, 09:58:54 > > Features: >CC: gcc, gcc (GCC) 4.0.2 20050808 (prerelease) > (Ubuntu 4.0.1-4ubuntu9) > CXX: g++, g++ (GCC) 4.0.2 20050808 (prerelease) > (Ubuntu 4.0.1-4ubuntu9) > CPPFLAGS: '' >CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W > -funit-at-a-time' > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > -fmessage-length=0 -funit-at-a-time' >build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu > Use dietlibc: yes >Build C++ programs: yes >Build C99 programs: yes >Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts > ext2fs Source: e2fsprogs > syscall(2) invocation: alternative > vserver(2) syscall#: 236/alternative > > Paths: >prefix: /usr > sysconf-Directory: /etc > cfg-Directory: /etc/vservers > initrd-Directory: $(sysconfdir)/init.d >pkgstate-Directory: /var/run/vservers > Kernelheaders: /usr/include > vserver-Rootdir: /var/lib/vservers > > > I want to set context disk limits with vdlimit, therefore I need the > tagxid mount option, did I get it right? how do I enabled tagxid > support? kernel option uid24/gid24 is set. yes, usually it's just a matter of: mount -o tagxid /dev/some /vservers best, Herbert > cu joh. > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc
On Wed, Feb 01, 2006 at 01:40:29PM -0500, Micah Anderson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Herbert Poetzl wrote: > >>Btw may I ask you to add this -n (i.e. no_color option) to testme. > >>That would look like: > > > > > > no problem, will put it into the next version ... > > > > thanks, > > Herbert > > I thought that the -n (no_color) option was added after I sent a similar > patch back in October[1]? yes, it was, but (if you read your mail again) only to the testfs.sh script, not the testme.sh one ... best, Herbert > Micah > > 1. http://list.linux-vserver.org/archive/vserver/msg10918.html > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2 (GNU/Linux) > > iD8DBQFD4QCd9n4qXRzy1ioRAtNAAJwJierglR+/ufpIpIUDaOsfQltKugCfVG0t > 1x55Xg0BgliW2mEDNE9TBCU= > =eGnX > -END PGP SIGNATURE- > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Herbert Poetzl wrote: >>Btw may I ask you to add this -n (i.e. no_color option) to testme. >>That would look like: > > > no problem, will put it into the next version ... > > thanks, > Herbert I thought that the -n (no_color) option was added after I sent a similar patch back in October[1]? Micah 1. http://list.linux-vserver.org/archive/vserver/msg10918.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD4QCd9n4qXRzy1ioRAtNAAJwJierglR+/ufpIpIUDaOsfQltKugCfVG0t 1x55Xg0BgliW2mEDNE9TBCU= =eGnX -END PGP SIGNATURE- ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?
Hello all, I started playing with vserver unification recently and I'd like to share my two observations: - under Debian (sarge at least) you cannot use the supplied beecrypt2 packages as they have a slightly different API (changes are subtle enough that util-vserver will compile but hashcalc will die with a segmentation fault). Use beecrypt4: http://prdownloads.sourceforge.net/beecrypt/beecrypt-4.0.0.tar.gz?download - If I modify a file's contents the CoW link is broken properly but after a chmod or chown the link is not broken and I get -EPERM (as the files are marked immutable) - is this expected behaviour? In such a situation the links aren't exactly CoW... Best regards, Grzegorz Nosek ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Can't rename vserver's host name
Hi there, on Wednesday, February 1, 2006 at 1:28:24 PM there was posted: GH> Whitin the vserver, /etc/hostname file contains "iserv" GH> Any ideas? Palce the hostname on the host in /etc/vservers/[vserver-name]/uts/nodename - this is the file which is used to "create" the hostname on boot. -- regards 'n greez, Guenther Fuchs (aka "muh" and "powerfox") ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] tagxid mount option
got vserver working and running some different machines, debian/ubuntu mixed. so, nice work guys! I could not mount with the tagxid option. system is running on: Versions: Kernel: 2.6.12-joh VS-API: 0x00020001 util-vserver: 0.30.208; Dec 3 2005, 09:58:54 Features: CC: gcc, gcc (GCC) 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9) CXX: g++, g++ (GCC) 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9) CPPFLAGS: '' CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time' CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time' build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu Use dietlibc: yes Build C++ programs: yes Build C99 programs: yes Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts ext2fs Source: e2fsprogs syscall(2) invocation: alternative vserver(2) syscall#: 236/alternative Paths: prefix: /usr sysconf-Directory: /etc cfg-Directory: /etc/vservers initrd-Directory: $(sysconfdir)/init.d pkgstate-Directory: /var/run/vservers Kernelheaders: /usr/include vserver-Rootdir: /var/lib/vservers I want to set context disk limits with vdlimit, therefore I need the tagxid mount option, did I get it right? how do I enabled tagxid support? kernel option uid24/gid24 is set. cu joh. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] increased security models
I'd like some input or suggestions or combining vservers with some security related patches. I've used vservers and grsecurity (on separate machines), and have dabbed in adamantix-style RSBAC with the debian provided patch package, but I don't have a deep enough vserver knowledge to know what are the 'official' vserver recommendations and which things it mixes well with, and which it doesn't. I'm aware that using vservers in itself solves a lot of problems chroot-wise, but it would still be nice to have pax, etc inside the vservers. So if you have some recommendations or thoughts about this I'd be glad to hear them. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Can't rename vserver's host name
Hi list, we have had a physical machine named iserv running with Suse Linux for quite a while. Now we have migrated the machine to a Debian vserver running in a Debian host (complete new install from scratch). When creating the vserver, I set vserver name=iserv but vserver *host* name=iservneu because it was necessary to run old physical Suse machine and new virtual Debian machine at the same time in the same network to migrate some user mailboxes to the new machine. Now, after the old Suse machine has been shut down forever I'd like to rename vserver host name from "iservneu" to "iserv". I found some older posts in this lists that claim there *should* be some file iserv.conf but I don't have it. Whitin the vserver, /etc/hostname file contains "iserv" When running hostname command without parameters in the vserver after a vserver reboot, "iservneu" is shown as hostname. Running "hostname iserv" does not help, after restart it still claims that host name is "iservneu". Any ideas? TIA Gerhard ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc
On Wed, Feb 01, 2006 at 07:48:25AM +0100, Joel Soete wrote: > Hello Herbert, > > The latest test seems always ok (I mean no regression imho) on this > parisc 32bit up kernel ;-) great! nitpick: let's prefix the tests with [ARCH] in the future (for ML postings) to simplify searching ... btw, we a planning to support an -m 'mail' option to send the arch info to the ML in the near future ... > Linux patst007 2.6.16-rc1-vs2.1.0.9-pa2-d32up #3 Tue Jan 31 08:16:56 CET 2006 > parisc GNU/Linux > Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl > chcontext is working. > chbind is working. > Linux 2.6.16-rc1-vs2.1.0.9-pa2-d32up #3 Tue Jan 31 08:16:56 CET 2006 parisc > Ea 0.30.209 263/fallback (S*) > VCI: 0002:0001 263 03000116 (TbLgnP) > --- > [000]# succeeded. > [001]# succeeded. > [011]# succeeded. > [031]# succeeded. > [101]# succeeded. > [102]# succeeded. > [201]# succeeded. > [202]# succeeded. > --- > [L01]# succeeded. > [D01]# succeeded. > [L02]# succeeded. > [D02]# succeeded. > [L03]# succeeded. > [D03]# succeeded. > [L11]# succeeded. > [D11]# succeeded. > [L12]# succeeded. > [D12]# succeeded. > [L21]# succeeded. > [D21]# succeeded. > [L22]# succeeded. > [D22]# succeeded. > [L31]# succeeded. > [D31]# succeeded. > > Linux-VServer FS Test [V0.12] Copyright (C) 2005-2006 H.Poetzl > Linux 2.6.16-rc1-vs2.1.0.9-pa2-d32up parisc/0.30.209 > VCI: 0002:0001 263 03000116 (ugid24) > --- > testing ext2 filesystem ... > [000]. (ext2 format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]. [106]. [108]. [109]. > [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. > [121]. [122]. [123]. [124]. [199]. > > --- > testing ext3 filesystem ... > [000]. (ext3 format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]. [106]. [108]. [109]. > [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. > [121]. [122]. [123]. [124]. [199]. > > --- > testing xfs filesystem ... > [000]. (xfs format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]. [106]. [108]. [109]. > [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. > [121]. [122]. [123]. [124]. [199]. > > --- > testing reiser filesystem ... > [000]. (reiserfs format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]. [106]. [108]. [109]. > [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. > [121]. [122]. [123]. [124]. [199]. > > --- > testing jfs filesystem ... > [000]. (jfs format) > xid related tests ... > [001]. [002]. [011]. [012]. [014]. [015]. [019]. > [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. > [033]. [034]. [035]. [037]. > xattr related tests ... > [101]. [102]. [103]. [104]* [106]. [108]. [109]. > [112]. [113]. [114]* [115]. [116]. [117]. [118]. [119]. > [121]* [122]* [123]* [124]* [199]. > > Btw may I ask you to add this -n (i.e. no_color option) to testme. > That would look like: no problem, will put it into the next version ... thanks, Herbert > # diff -Nau testme.sh.Orig testme.sh > --- testme.sh.Orig 2006-01-31 13:46:09.0 +0100 > +++ testme.sh 2006-01-31 14:03:20.0 +0100 > @@ -69,13 +69,14 @@ > > > verbose=0 > -while getopts ":hqvA:L" option; do > +while getopts ":hnqvA:L" option; do >case $option in > h) # help > cat << EOF > Usage: $cmdname [OPTION]... > >-hhelp > + -nno color codes >-qquick test >-v be verbose >-A [ARCH] architecture specific tests > @@ -92,6 +93,10 @@ > q) # just do quick tests > quick=1 > ;; > +n) # no color > +eR='';eG='';eY='';eB='';eN='' > +nocolor=1; > +;; > v) # be verbose > verbose=$(( verbose + 1 )) > ;; > <> > > TIA&HTH, > Joel > > --- > NOTE! My email address is changing to ... @scarlet.be > Please make the necessary changes in your address book. > > ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] please avoid vs2.1.0.5-vs2.1.0.7 ...
Mike O'Connor wrote: Hi Martin http://vserver.13thfloor.at/Experimental/patch-2.6.15-vs2.1.0.5.1.diff This file seems to be missing. http://vserver.13thfloor.at/Experimental/patch-2.6.15.1-vs2.1.0.5.1.diff ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] 2.6.16-rc1-vs2.1.0.9 latest test on parisc
Hello Herbert, The latest test seems always ok (I mean no regression imho) on this parisc 32bit up kernel ;-) Linux patst007 2.6.16-rc1-vs2.1.0.9-pa2-d32up #3 Tue Jan 31 08:16:56 CET 2006 parisc GNU/Linux Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl chcontext is working. chbind is working. Linux 2.6.16-rc1-vs2.1.0.9-pa2-d32up #3 Tue Jan 31 08:16:56 CET 2006 parisc Ea 0.30.209 263/fallback (S*) VCI: 0002:0001 263 03000116 (TbLgnP) --- [000]# succeeded. [001]# succeeded. [011]# succeeded. [031]# succeeded. [101]# succeeded. [102]# succeeded. [201]# succeeded. [202]# succeeded. --- [L01]# succeeded. [D01]# succeeded. [L02]# succeeded. [D02]# succeeded. [L03]# succeeded. [D03]# succeeded. [L11]# succeeded. [D11]# succeeded. [L12]# succeeded. [D12]# succeeded. [L21]# succeeded. [D21]# succeeded. [L22]# succeeded. [D22]# succeeded. [L31]# succeeded. [D31]# succeeded. Linux-VServer FS Test [V0.12] Copyright (C) 2005-2006 H.Poetzl Linux 2.6.16-rc1-vs2.1.0.9-pa2-d32up parisc/0.30.209 VCI: 0002:0001 263 03000116 (ugid24) --- testing ext2 filesystem ... [000]. (ext2 format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]. [106]. [108]. [109]. [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. [121]. [122]. [123]. [124]. [199]. --- testing ext3 filesystem ... [000]. (ext3 format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]. [106]. [108]. [109]. [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. [121]. [122]. [123]. [124]. [199]. --- testing xfs filesystem ... [000]. (xfs format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]. [106]. [108]. [109]. [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. [121]. [122]. [123]. [124]. [199]. --- testing reiser filesystem ... [000]. (reiserfs format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]. [106]. [108]. [109]. [112]. [113]. [114]. [115]. [116]. [117]. [118]. [119]. [121]. [122]. [123]. [124]. [199]. --- testing jfs filesystem ... [000]. (jfs format) xid related tests ... [001]. [002]. [011]. [012]. [014]. [015]. [019]. [020]. [021]. [022]. [023]. [024]. [025]. [026]. [027]. [028]. [033]. [034]. [035]. [037]. xattr related tests ... [101]. [102]. [103]. [104]* [106]. [108]. [109]. [112]. [113]. [114]* [115]. [116]. [117]. [118]. [119]. [121]* [122]* [123]* [124]* [199]. Btw may I ask you to add this -n (i.e. no_color option) to testme. That would look like: # diff -Nau testme.sh.Orig testme.sh --- testme.sh.Orig 2006-01-31 13:46:09.0 +0100 +++ testme.sh 2006-01-31 14:03:20.0 +0100 @@ -69,13 +69,14 @@ verbose=0 -while getopts ":hqvA:L" option; do +while getopts ":hnqvA:L" option; do case $option in h) # help cat << EOF Usage: $cmdname [OPTION]... -hhelp + -nno color codes -qquick test -v be verbose -A [ARCH] architecture specific tests @@ -92,6 +93,10 @@ q) # just do quick tests quick=1 ;; +n) # no color +eR='';eG='';eY='';eB='';eN='' +nocolor=1; +;; v) # be verbose verbose=$(( verbose + 1 )) ;; <> TIA&HTH, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] postfix starttls problem in a vserver
Thanks for those /tmp suggestions, for time being I decided to stick with /tmp in RAM. Now I'm having some strange connection warning in postfix logs. Before I run over to the postfix mailing lists, has anyone ran into Feb 1 11:32:01 v64 postfix/smtp[23512]: warning: connect to private/tlsmgr: No such file or directory Feb 1 11:32:02 v64 postfix/smtp[23512]: warning: connect to private/tlsmgr: No such file or directory Feb 1 11:32:02 v64 postfix/smtp[23512]: warning: problem talking to server private/tlsmgr: No such file or directory Feb 1 11:32:02 v64 postfix/smtp[23512]: warning: no entropy for TLS key generation: disabling TLS support on a vserver? -- Eugen* Leitl http://leitl.org";>leitl http://leitl.org __ ICBM: 48.07100, 11.36820http://www.ativel.com 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE signature.asc Description: Digital signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
