05.02.2013 05:10, Stéphane Graber wrote:
dwight.en...@oracle.com: host aserp1030.oracle.com[141.146.126.68] said:
554
5.3.0 5.7.1 Permanently rejected due to our anti-spam policies. (in
reply
to MAIL FROM command)
(this is about isrv.corpit.ru[86.62.121.231] - our mail host).
On 29.05.2012 02:02, richard -rw- weinberger wrote:
Hi!
Is there any use case where a user wants to omit -f?
In my case I didn't use -f, but later resorted to using
-f /dev/null to be sure. So this is yet another me too,
I guess. Maybe there should be more well-defined behavour
about what
On 11.05.2012 20:59, Ward, David - 0663 - MITLL wrote:
[]
In the container, could you create a MACVLAN interface in bridge mode
attached to your 10Gb Ethernet interface, instead of going through a
bridge device? I would expect that to perform better.
FWIW, I tested macvlan vs bridge in the
On 02.11.2011 03:51, Eric W. Biederman wrote:
[]
And having CAP_MKNOD in container may not be that bad either, while
cgroup device.permission is set correctly - some nodes may need to
be created still, even in an unprivileged containers. Who filters
out CAP_MKNOD during container startup (I
On 02.09.2011 00:46, Daniel Lezcano wrote:
On 09/01/2011 09:30 PM, Nico wrote:
Hi,
I just wanted to give it a try again with lxc after one year,
this is so bad same bugs are always here :
* you can do a mount -o romount,ro / inside container (reported
since first times ... :( ),
and host
11.03.2011 22:47, richard -rw- weinberger пишет:
hi,
i'm using this minimal config:
lxc.utsname = c0
lxc.mount.entry = none /lxc/c0/proc proc defaults 0 0
lxc.rootfs = /lxc/c0/
but lxc does not mount proc into /lxc/c0/proc.
using lxc.mount = /path/to/fstab also does not work.
it's also
Daniel, this is this part:
conf.c:mount_entry_on_absolute_rootfs():
aux = strstr(mntent-mnt_dir, rootfs-path);
snprintf(path, MAXPATHLEN, %s%s, rootfs-mount,
aux + strlen(rootfs-path));
if rootfs-path ends with a slash we happily eat it,
producing this in
[resending to the correct address; lxc-users@ bounced]
On 20.01.2011 19:09, Jean-Philippe Menil wrote:
Hi,
i've just found something that is being anoying me:
when i restart the snmpd daemon on my host, it shutdown the snmpd daemon
on my container.
This, and many similar cases, happens
09.12.2010 18:29, Menil Jean-Philippe wrote:
Hi,
i'm experiencing some packet loss under high network traffic.
Here is the scenario:
i have on host with one guest running as a proxy (squid)
So, when i start downloading 10-15 dvd image from my client (wget
23.11.2010 13:25, Michael Tokarev wrote:
Hello again.
I asked this question before, but got no (satisfactory)
answer. So here it goes again.
Why not chdir into the root of container right when
the root filesystem is (bind-)mounted, and let all
mount entries to be relative
Stefan Tomanek wrote:
Dies schrieb Michael Tokarev (m...@tls.msk.ru):
[]
There's apparently no reason to run a script before
creating a netdev (pair). Note that we don't even
know which names will be used for the netdevs, at
least in general case.
I know, but there might be a point
Stefan Tomanek wrote:
Dies schrieb Daniel Lezcano (daniel.lezc...@free.fr):
Are we sure, we want to add these hooks (pre and post) ? I am not
against adding them, but IMO it is more sane to add them if needed
rather than adding something which may not be used.
Well, until now, there was
08.10.2010 19:45, Daniel Lezcano wrote:
[]
There IS a trivial way to extend system already (when
just ONE hook is implemented) - chain your scripts.
There's no need to re-implement shell in lxc.
Michael, I am not sure I get the idea. Can you elaborate a bit ?
In our case, we need the
06.10.2010 12:06, Stefan Tomanek wrote:
Hello,
I'd like to use lxc for containing virtual debian instances, using the veth
networking method. Due to the network topology employed, I do not want to use
a
bridge to connect the virtual devices to the real network, but set individual
host
Daniel Lezcano wrote:
Michael Tokarev wrote:
lxc-start: No such file or directory - failed to mount a new instance
of '/dev/pts'
I'm experimenting with a read-only root fs in the container.
So far it does not work.
First of all, when trying to start a container in a read-only root
lxc
lxc-start: No such file or directory - failed to mount a new instance of
'/dev/pts'
I'm experimenting with a read-only root fs in the container.
So far it does not work.
First of all, when trying to start a container in a read-only root
lxc-start complains:
lxc-start: Read-only file system -
16 matches
Mail list logo
