Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S slapos.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slapos.core
  • Merge requests
  • !11

Open
Created Jan 10, 2017 by Nicolas Wavrant@NicolasMaintainer
  • Report abuse
Report abuse

WIP: SlapObject: when destroying a partition, no residues from user activity should remain

  • Overview 6
  • Commits 2
  • Changes 1

When users connect to a slappart by ssh, they can run or plan tasks running in the background. As these aren't run by supervisord, they are not stopped when the slappart is destroyed, and they remain even when the slappart is attributed to another user.

In the consequence of this, instanciation errors can appear later if the services run in background are using some ports that the new user wants also to use, or even worst.

This patch proposes to kill all the processes belonging to the slapuser when its slappart is destroyed, and clean the user's crontabs and at jobs.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: slapgrid-process-management
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7