1. 13 Nov, 2009 2 commits
    • Allows a container to run without previous creation · 48862401
      Daniel Lezcaon authored
      When a container was created, its configuration is used.
      When a container was not created, the configuration specified in
      the command line is used, if not configuration file is used,
      default values are used.
      
      That allows to create 'volatile' container, like tmp files.
      It is useful for example to spawn different container with the
      same generic configuration file. That let the user to have its own
      repository of configuration files.
      
      And, more important, that fix temporary created container with
      lxc-execute to be not deleted when the host crash or the command
      is killed.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • liblxc: Fix compile failure · 6dadd7dc
      Dhaval Giani authored
      Fix compile failure
      
      commit 884866b3 introduces a compile
      failure,
      
      make[3]: *** No rule to make target `lock.c', needed by `liblxc_so-lock.o'.  Stop.
      make[3]: Leaving directory `/home/dhaval/work/lxc/lxc/src/lxc'
      make[2]: *** [all-recursive] Error 1
      make[2]: Leaving directory `/home/dhaval/work/lxc/lxc/src'
      make[1]: *** [all] Error 2
      make[1]: Leaving directory `/home/dhaval/work/lxc/lxc/src'
      make: *** [all-recursive] Error 1
      
      Remove those entries from the Makefile
      Signed-off-by: 's avatarDhaval Giani <dhaval@linux.vnet.ibm.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  2. 12 Nov, 2009 3 commits
  3. 11 Nov, 2009 1 commit
  4. 09 Nov, 2009 1 commit
  5. 04 Nov, 2009 2 commits
    • lxc: lxc version to reflect string in AC_INIT (V2) · d5cf4386
      Michel Normand authored
      I changed the code to have lxc version to reflect the
      string set in AC_INIT of configure.ac
      rather than to report only the 3 first digits
      
      update: use PACKAGE_VERSION in place of VERSION
      Signed-off-by: 's avatarMichel Normand <normand@fr.ibm.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • configure.ac - allow user to switch off/on documentation generation · 5c8f9bd8
      Andrian Nord authored
      Andrian Nord <NightNord@gmail.com>:
      >> > > As documentation requires docbook2man to be installed, which is not,
      >> > > otherwise, required for proper LXC work or compilation process, it
      >> > > might be usefull to be able to switch it off.
      
      Michel Normand <normand@fr.ibm.com>:
      > > For me, it is Ok to add a --enable/disable/-doc,
      > > but not make configure to fail if no option specified
      > > and no docbook2man package.
      > > 
      > > For me it should be optionnal.
      > > I like the current behaviour where configure is running without option
      > > and is enabling/disabling by itself the doc building.
      > > Could you send a new patch with this idea ?
      
      Andrian Nord <NightNord@gmail.com>:
      Of course. You mean, that you what default behaviour to remain
      auto-detection? That is:
      --enable-doc: require docbook2man or fail, generate mans
      --enable-doc=auto, or not specified (default): check for docbook2man,
      generate mans if found, silently ignore if not found (I suppose
      diagnostic message is redundant, as information already contains into
      ./configure --help)
      --disable-doc: never check for docbook2man and don't gen mans
      
      Here comes a patch what do this, as far as I see
      (I'm sorry for violating post-rules in previous mail, now I'll do all
      right, I hope. Should I attach patch anyway, as it might be usefull
      for applying?)
      Signed-off-by: 's avatarAndrian Nord <NightNord@gmail.com>
      Acked-by: 's avatarMichel Normand <normand@fr.ibm.com>
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
  6. 03 Nov, 2009 1 commit
  7. 23 Oct, 2009 1 commit
  8. 22 Oct, 2009 3 commits
  9. 15 Oct, 2009 1 commit
  10. 12 Oct, 2009 4 commits
  11. 09 Oct, 2009 18 commits
  12. 07 Oct, 2009 3 commits
    • make container to die when parent dies · 6a6ad7af
      Daniel Lezcano authored
      When the parent of the first process dies, the container stays there
      making very difficuly to track it and to kill. We have to use the
      lxc-ps --lxc and kill the processes, hoping we kill the init process
      of the container. That's not a big deal until we have thousand of
      processes in the container :)
      
      We want to keep the parent of the container init always there, this
      process is responsible to manage the container, provide tty, notify
      the container changing states and ensure self exclusion (eg. avoid
      to launch several containers with the same name).
      
      If this process dies, we consider that as a fatal error and we make
      the child process to die too. This patch will just add the prctl to
      to send a SIGKILL to the container init process when its parent exits
      For the point of view of the pid namespace, when the init process dies
      all the processes of the namespace are killed too.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • Simplify the mainloop · a9e61274
      Daniel Lezcano authored
      The number of fds passed to epoll is just a hint for the kernel.
      In our case, we know this is often 2, let's remove this parameter
      from lxc_mainloop_open and cleanup the code around the caller of
      this function.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>
    • format and fix small typos · ded1d23f
      Daniel Lezcano authored
      Indent and make the code cleaner.
      Signed-off-by: 's avatarDaniel Lezcano <dlezcano@fr.ibm.com>