Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • emulab-devel emulab-devel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 160
    • Issues 160
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emulab
  • emulab-develemulab-devel
  • Repository
Switch branch/tag
  • emulab-devel
  • clientside
  • tmcc
  • common
  • vnodesetup
Find file BlameHistoryPermalink
  • Leigh B Stoller's avatar
    Signal handling changes to deal with openvz containers that will not · e708a846
    Leigh B Stoller authored Sep 28, 2012
    die. Mostly a workaround, since I do not know why the signal that was
    sent is not delivered when mkvnode unblocks them. So, just send the
    signal multiple times. Gack. Needs a lot more thought!
    e708a846