Ferenc Wagner wrote:
> Daniel Lezcano writes:
>
>> Ferenc Wagner wrote:
>>
>>> I can see that lxc-unshare isn't for me: I wanted to use it to avoid
>>> adding the extra lxc-start process between two daemons communicating via
>>> signals, but it's impossible to unshare PID namespaces, so I'm doome
Daniel Lezcano writes:
> Ferenc Wagner wrote:
>
>> I can see that lxc-unshare isn't for me: I wanted to use it to avoid
>> adding the extra lxc-start process between two daemons communicating via
>> signals, but it's impossible to unshare PID namespaces, so I'm doomed.
>
> There is a pending p
Hi everybody,
I have just started playing with lxc and having some difficulties to set cpu
and memory on my guests. After my searches, seems that resources controlling
is managing in cgroup files and I think that I missed something or I didn't
understand how deal with cgroup.
After reading cgroup
Ferenc Wagner wrote:
> Hi,
>
> While playing with lxc-start, I noticed that /tmp is infested by empty
> lxc-r* directories:
>
> # lxc-start --logfile=/tmp/startlog --logpriority=DEBUG -n jail -s
> lxc.mount.entry="/ /tmp/jail none bind 0 0" -s lxc.rootfs=/tmp/jail -s
> lxc.pivotdir=/mnt ls /proc
Ferenc Wagner wrote:
> Hi,
>
> as of git 305bc646, the following happens:
>
> # strace -f lxc-unshare -s NETWORK
> [...]
> clone(Process 3085 attached (waiting for parent)
> Process 3085 resumed (parent 3084 ready)
> child_stack=0xbfe836d4, flags=0x4000|SIGCHLD) = 3085
> [pid 3085] getpid()
Hi,
While playing with lxc-start, I noticed that /tmp is infested by empty
lxc-r* directories:
# lxc-start --logfile=/tmp/startlog --logpriority=DEBUG -n jail -s
lxc.mount.entry="/ /tmp/jail none bind 0 0" -s lxc.rootfs=/tmp/jail -s
lxc.pivotdir=/mnt ls /proc
# cat /tmp/startlog
lxc-start
Hi,
as of git 305bc646, the following happens:
# strace -f lxc-unshare -s NETWORK
[...]
clone(Process 3085 attached (waiting for parent)
Process 3085 resumed (parent 3084 ready)
child_stack=0xbfe836d4, flags=0x4000|SIGCHLD) = 3085
[pid 3085] getpid()= 3085
[pid 3085] ---
