1. 11 Apr, 2018 3 commits
  2. 10 Apr, 2018 2 commits
  3. 09 Apr, 2018 7 commits
  4. 07 Apr, 2018 1 commit
  5. 06 Apr, 2018 4 commits
  6. 05 Apr, 2018 1 commit
  7. 04 Apr, 2018 1 commit
    • fix signal sending in lxc.init · 9cb94384
      Tycho Andersen authored
      The problem here is that these two clauses were ordered backwards: we first
      check if the signal came from not the init pid, and if it did, then we give
      a notice and return. The comment notes that this is intended to protect
      against SIGCHLD, but we don't in fact know if the signal is a SIGCHLD yet,
      because that's tested in the next hunk.
      
      The symptom is that if I e.g. send SIGTERM from the outside world to the
      container init, it ignores it and gives this notice. If we re-order these
      clauses, it forwards non SIGCHLD signals, and ignores SIGCHLD signals from
      things that aren't the real container process.
      Signed-off-by: 's avatarTycho Andersen <tycho@tycho.ws>
  8. 03 Apr, 2018 2 commits
  9. 02 Apr, 2018 3 commits
  10. 31 Mar, 2018 1 commit
  11. 30 Mar, 2018 3 commits
  12. 29 Mar, 2018 5 commits
  13. 28 Mar, 2018 1 commit
  14. 27 Mar, 2018 5 commits
  15. 26 Mar, 2018 1 commit