Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xterm and nomachine not in cgroup #28

Closed
jeremyfix opened this issue Nov 22, 2021 · 2 comments
Closed

xterm and nomachine not in cgroup #28

jeremyfix opened this issue Nov 22, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@jeremyfix
Copy link
Owner

As xterm and nomachine are not aware of the group, every process running in these processes are not aware of the ressources restriction.

This does not apply to VNC because vncserver is ran from within the srun session

For xterm, one workaround could be to allow x11 for the ssh connection from which we trigger the srun command and modify the srun call with --x11 in the srun command.

For NoMachine, I do not know yet for any workaround. At least, we should deactivate the NoMachine action if we do not run with "exclusive" allocation.

@jeremyfix jeremyfix added the bug Something isn't working label Nov 22, 2021
@jeremyfix
Copy link
Owner Author

One, probably better way to solve that problem is to allocate with salloc rather than srun and then launch commands within srun :

  • we ssh -X on the frontal node, and then allocate with salloc -N 1 --x11 ..
  • in another ssh session, we can trigger a command requiring x11 as : ssh frontal "SLURM_JOB_ID=4117 srun xeyes", where, in this example , 4117 was the job id returned by the salloc

Note that, possibly, as soon as the ssh session with the salloc is closed, the allocation is released. Maybe, if we run the salloc within a screen session, that could keep it alive.

@jeremyfix
Copy link
Owner Author

Fixed on server side ;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant