On 05/24/2013 02:06 AM, Daniel Lezcano wrote:
> Yes, sure.
>
> Sorry, I have been more and more busy with other stuff and flooded by
> emails, so I did not followed the discussion closely.
>
> Can you explain in a few words what do you need ?
>
I'd like to be sure, there is no SPOF in the listadmi
On Fri, 2013-05-24 at 02:06 +0200, Daniel Lezcano wrote:
> On 05/23/2013 11:44 PM, Tamas Papp wrote:
> > On 05/23/2013 11:13 PM, Michael H. Warfield wrote:
> >> Last I knew, it was Daniel who created the list and most likely "owns"
> >> it. It was created at my suggestion to move "user" questions
On 05/23/2013 11:44 PM, Tamas Papp wrote:
> On 05/23/2013 11:13 PM, Michael H. Warfield wrote:
>> Last I knew, it was Daniel who created the list and most likely "owns"
>> it. It was created at my suggestion to move "user" questions off the
>> "devel" list ages and ages ago. Lately he's typically
further notes:
i had to allow lxc/console, lxc/tty1 etc in /etc/securetty
sshd login doesnt work:
Read from socket failed: Connection reset by peer
auth.log: May 23 23:50:21 test4 sshd[1187]: fatal: setgroups: Invalid
argument [preauth]
debug output doesnt say more, do you have an idea? thanks
On 05/23/2013 11:13 PM, Michael H. Warfield wrote:
> Last I knew, it was Daniel who created the list and most likely "owns"
> it. It was created at my suggestion to move "user" questions off the
> "devel" list ages and ages ago. Lately he's typically been "buried over
> his head" busy that he doe
On Thu, 2013-05-23 at 22:33 +0200, Tamas Papp wrote:
> hi Guys,
> Please, someone!
> Who is the owner/admin of this list?
Last I knew, it was Daniel who created the list and most likely "owns"
it. It was created at my suggestion to move "user" questions off the
"devel" list ages and ages ago. L
Quoting Tamas Papp (tom...@martos.bme.hu):
> On 05/23/2013 09:47 PM, Serge Hallyn wrote:
> >The lxc lock had nothing to do with the segfaulting - and no, the new
> >hanges will simply swap out use of named semaphore for a flock on an
> >open fd (so that they get auto-cleaned if process is killed).
Quoting Vallevand, Mark K (mark.vallev...@unisys.com):
> Very good point. The syslog server always recreates the sockets when it
> starts.
>
> I think I'll stay with what I have working.
Yeah that sounds best :)
--
Try
hi Guys,
Please, someone!
Who is the owner/admin of this list?
Thanks,
tamas
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delive
hi,
lxc-ls --fancy-format is case sensitivie:
$ lxc-ls --fancy --fancy-format name,state,ipv4,autostart
NAME STATEIPV4AUTOSTART
According to the above headers the suspected format is uppercase (I thin).
lxc-info --state-is is
Very good point. The syslog server always recreates the sockets when it starts.
I think I'll stay with what I have working.
Regards.
Mark K Vallevand mark.vallev...@unisys.com
May you live in interesting times, may you come to the attention of important
people and may all your wishes come tr
Good to know.
Regards.
Mark K Vallevand mark.vallev...@unisys.com
May you live in interesting times, may you come to the attention of important
people and may all your wishes come true.
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only
On 05/23/2013 09:47 PM, Serge Hallyn wrote:
> The lxc lock had nothing to do with the segfaulting - and no, the new
> hanges will simply swap out use of named semaphore for a flock on an
> open fd (so that they get auto-cleaned if process is killed). Any
> potential for segvs *should* be found whi
On 05/23/2013 09:42 PM, Vallevand, Mark K wrote:
> Will that work for a single file? I thought it was for directories.
>
>
It works for files, but I would use parent directories for the syslog sockets,
since sockets are
changing eg. by restarting the syslog server.
tamas
-
Quoting Vallevand, Mark K (mark.vallev...@unisys.com):
> Will that work for a single file? I thought it was for directories.
Yup, you can bind mount files.
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic
Quoting Tamas Papp (tom...@martos.bme.hu):
> On 05/23/2013 07:55 PM, Serge Hallyn wrote:
> >>FYI, now it works fine now with
> >>0.9.0.0~staging~20130523-0240-0ubuntu1~ppa1~precise1 .
> >>For this I had to stop all containers then start them again.
> >Ok - I
Will that work for a single file? I thought it was for directories.
Regards.
Mark K Vallevand mark.vallev...@unisys.com
May you live in interesting times, may you come to the attention of important
people and may all your wishes come true.
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OT
Quoting Vallevand, Mark K (mark.vallev...@unisys.com):
> Here is how I got syslog to work with a program running in a container.
> After creating a container, do something like this:
>
> echo syslog setup
> cat < /etc/rsyslog.d/99-lxc-1.conf
> \$AddUnixListenSocket /var/lib/lxc/container1/rootfs
On 05/23/2013 07:55 PM, Serge Hallyn wrote:
>> FYI, now it works fine now with
>> 0.9.0.0~staging~20130523-0240-0ubuntu1~ppa1~precise1 .
>> For this I had to stop all containers then start them again.
> Ok - I suspect what was happening was that every lxc-ls was
> segfa
Here is how I got syslog to work with a program running in a container. After
creating a container, do something like this:
echo syslog setup
cat < /etc/rsyslog.d/99-lxc-1.conf
\$AddUnixListenSocket /var/lib/lxc/container1/rootfs/dev/log
EOF
restart rsyslog
If you are using rsyslog, of course.
ll be there, as the intent is to keep
> > two programs which are both doing c->set_config_item("lxc.rootfs", x)
> > from overwiting each other.
> >
> > I'll try to get the replacement for that ready for staging by
> > tomorrow night.
>
> FYI, n
is holding the lock, you
> may have to remove it manually. If the commands are still running,
> then of course they should still be there, as the intent is to keep
> two programs which are both doing c->set_config_item("lxc.rootfs", x)
> from overwiting each other.
>
> I&
Quoting Tamas Papp (tom...@martos.bme.hu):
> On 05/23/2013 03:39 PM, Tamas Papp wrote:
> > On 05/23/2013 03:35 PM, Stéphane Graber wrote:
> >> That looks like broken locking, though Serge would know for sure.
> >> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
> >> problem (n
Quoting Niklas Fuchs (nkfu...@yahoo.de):
> On Wed, May 22, 2013 at 03:36:41PM -0500, Serge Hallyn wrote:
> > Did you create the container with just 'sudo lxc-create -t ubuntu -n r1'?
> > Is lxc.ttydir set to lxc in the configuration file?
> sorry, i gave you wrong information. it was a debian templ
On 05/23/2013 03:39 PM, Tamas Papp wrote:
> On 05/23/2013 03:35 PM, Stéphane Graber wrote:
>> That looks like broken locking, though Serge would know for sure.
>> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
>> problem (not usually recommended as those locks are there for a
On 05/23/2013 03:35 PM, Stéphane Graber wrote:
> That looks like broken locking, though Serge would know for sure.
> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
> problem (not usually recommended as those locks are there for a reason).
OK.
At this moment I'm trying to re
On 05/23/2013 01:46 AM, Tamas Papp wrote:
> On 05/23/2013 04:27 AM, Stéphane Graber wrote:
>> Oops, looks like I broke lxc-ls --fancy with my recent get_ips() API
>> change. I'll fix it directly to staging (trivial fix) and trigger a new
>> daily build, you should be able to update to a fixed packa
On Wed, May 22, 2013 at 03:36:41PM -0500, Serge Hallyn wrote:
> Did you create the container with just 'sudo lxc-create -t ubuntu -n r1'?
> Is lxc.ttydir set to lxc in the configuration file?
sorry, i gave you wrong information. it was a debian template. ubuntu
really worked.
i got debian working
On 05/22/13 15:44, Harald Dunkel wrote:
> Hi folks,
>
> If I run 'halt' in the container, then init does not
> terminate. I have to switch to the host to kill the
> container. This is pretty painful.
>
Obviously this is a problem of Debian's sysvinit, see
http://bugs.debian.org/706676 .
Thanx a
29 matches
Mail list logo
